#BROKER_URL = "sqla+sqlite:///celerydb.sqlite"
BROKER_URL = "redis://localhost:6379/0"
CELERY_IMPORTS = ("superset.sql_lab", "superset.tasks")
#CELERY_RESULT_BACKEND = "db+sqlite:///celery_results.sqlite"
CELERYD_LOG_LEVEL = "DEBUG"
CELERYD_PREFETCH_MULTIPLIER = 1
CELERY_ACKS_LATE = False
CELERY_ANNOTATIONS = {
"sql_lab.get_sql_results": {"rate_limit": "100/s"},
"email_reports.send": {
"rate_limit": "1/s",
"time_limit": 120,
"soft_time_limit": 150,
"ignore_result": True,
},
}
CELERYBEAT_SCHEDULE = {
"email_reports.schedule_hourly": {
"task": "email_reports.schedule_hourly",
"schedule": crontab(minute=55, hour="*"),
}
}
qlalchemy.exc.ProgrammingError: (psycopg2.ProgrammingError) column dbs.perm does not exis
superset db upgrade
I get the following:
sqlalchemy.exc.InternalError: (psycopg2.InternalError) cannot drop table report_schedule because other objects depend on it
DETAIL: constraint report_execution_log_report_schedule_id_fkey on table report_execution_log depends on table report_schedule
constraint report_recipient_report_schedule_id_fkey on table report_recipient depends on table report_schedule
constraint report_schedule_user_report_schedule_id_fkey on table report_schedule_user depends on table report_schedule
HINT: Use DROP ... CASCADE to drop the dependent objects too.
We are currently amidst a situation, where we want our Dashboard/chart owners to share their dashboard to only a specific set of user, to whom the owner decides to share it with (also some sort of audit for the owners to know who and all have access to dashboard ) .
Version: 0.37.2
Deployed: Google Kubernetes engine & on prem
Authentication: Oauth
Role: Custom role for all normal users (Gamma + sql lab role)
Database: Connection to presto only
Meta store : Postgres (stand alone outside Gke)
Notes : Each user have their own unique database connection to the same presto . Hence the data source permissions for charts are assigned manually for now . We need to automate the permission
Primary concern : The user should to whom the dashboard is shared should only have read access . also some sort of audit for the owners to know who and all have access to dashboard
PUBLIC_ROLE_LIKE = "Gamma"
and provided all required permissions in the public role, yet when i try to view the dashboard without logging in it fails with Unexpected Error
Have a quick question on chart loading time improvements with redis caching activated. I have the following caching parameters setup in my superset_config.py
file
CACHE_CONFIG = {
'CACHE_TYPE': 'redis',
'CACHE_DEFAULT_TIMEOUT': 60 * 60 * 24, # 1 day default (in secs)
'CACHE_KEY_PREFIX': 'superset_results',
'CACHE_REDIS_URL': 'redis://localhost:6379/0',
}
DATA_CACHE_CONFIG = {
'CACHE_TYPE': 'redis',
'CACHE_DEFAULT_TIMEOUT': 60 * 60 * 24, # 1 day default (in secs)
'CACHE_KEY_PREFIX': 'superset_results',
'CACHE_REDIS_URL': 'redis://localhost:6379/0',
}
And tested this against the World bank's data
dashboard. With an without caching, I am getting about 250 ~ 700 ms load time from watching the network response times in firefox for chart queries. Curious to see what performance numbers are others are seeing with caching on vs off
I'm running a redis + postgres on a metal server and superset in docker.