1991ec6e9bd3 apache/superset:latest-dev "/app/docker/docker-…" 17 hours ago Up 5 minutes (unhealthy) 8088/tcp superset_worker
80e0e565f0f3 apache/superset:latest-dev "/app/docker/docker-…" 17 hours ago Up 5 minutes (healthy) 0.0.0.0:8088->8088/tcp, :::8088->8088/tcp superset_app
b2a151609df5 apache/superset:latest-dev "/app/docker/docker-…" 17 hours ago Up 4 minutes (unhealthy) 8088/tcp superset_worker_beat
a4df52b39dba postgres:10 "docker-entrypoint.s…" 17 hours ago Up 5 minutes 5432/tcp superset_db
27baf7be3eef redis:latest "docker-entrypoint.s…" 17 hours ago Up 5 minutes 6379/tcp superset_cache
All-In-One, free resources and collections related to javascript. we provide useful links to help you learn JavaScript, web development and other related stuff along with some of the best resources available online.
SMTP_HOST = "smtp.gmail.com"
SMTP_STARTTLS = True
SMTP_SSL = False
SMTP_USER = "XXXXXXX"
SMTP_PORT = 587
SMTP_PASSWORD = "XXXXXXX"
SMTP_MAIL_FROM = "XXXXXXX"
Hey all - creating an API workflow for auto-generating dashboards. Context: ML model monitoring for our enterprise. Problem: Currently stuck on generating a query_context for a POST api/v1/chart/ request, based off of a saved_query.
Is there a defined way of generating this query_context? Or example repos containing a programatic workflow that I could refer to instead?
I installed sqlalchemy-trino and trino(trino-python-client) before deploying Superset, and I saw the message when I connected with my Trino cluster: "connection looks good."
And I also saw the schema and table through the connection with Trino in SQL lab .
But when I executed a query to Trino, I got an error: "
__init__() got an unexpected keyword argument 'user'."
Hi there, we are looking into working ob the current Alert/Reports area to
1) Use the Alert/Report Owner to generate the Data within the Celery Worker Code as we are using Row Level Security for Multi Tentant Type Integration
2) Add a S3 Data Drop as an addition to the already available Email and Slack
3) Use the Chart Data API to use a configured Chart Context instead of the pre-set Chart Context
We want to do this based on 1.5.0 Code at this time.
- Are there any instructions available what we need to take into consideration when forking, etc ?
- Is there a a responsible group of people that are working on this area (Alerts / Reports) to make sure our approaches are okay ?
Thanks, Mark
I have set a macro in my superset.py like this :
def get_graindate(col):
return "(case "+'{{ time_grain }}'+" when 'P1Y' then year("+col+") when 'P1M' then month("+col+") when 'P1D' then day("+col+") end)"
JINJA_CONTEXT_ADDONS = {
'graindate': lambda col: get_graindate(col),
}but '{{ time_grain }}' is alway undefined.
if i do select '{{ time_grain }}' it give me 'P1Y',
is it possible to pass '{{ time_grain }}' in parameter like thisgraindate('date_time', '{{ time_grain }}')` <= (i'v tried this but no luck) ?
Thanks for your help, it make me crazy 😝
