You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "Nimishbansal-16 (via GitHub)" <gi...@apache.org> on 2025/06/26 06:32:16 UTC
[D] Unable to activate async querying in superset 5.0.0 [superset]
GitHub user Nimishbansal-16 created a discussion: Unable to activate async querying in superset 5.0.0
I am trying to enable async querying using celery in the latest superset version 5.0.0.
These are my configurations -
Superset version: 5.0.0
superset_config.py -
GLOBAL_ASYNC_QUERIES_JWT_SECRET = {some_value}
FEATURE_FLAGS = {
"HORIZONTAL_FILTER_BAR": True,
"DRILL_TO_DETAIL": True,
"DASHBOARD_CACHE" : True,
"EMBEDDED_SUPERSET": True,
"ENABLE_ASYNC_QUERY_EXECUTION": True,
"GLOBAL_ASYNC_QUERIES": True
}
class CeleryConfig(object):
broker_url = "redis://:{user}@{ip}:{port}/{db}"
imports = (
"superset.sql_lab",
"superset.tasks.scheduler",
)
result_backend = "db+mysql://{user}:{pass}@{ip}:{port}/{db}"
worker_prefetch_multiplier = 10
task_acks_late = True
# broker_connection_retry_on_startup = True
task_annotations = {
"sql_lab.get_sql_results": {
"rate_limit": "100/s",
},
}
task_default_queue = 'superset_queue'
task_default_routing_key = 'superset.tasks'
task_queues = (
Queue('superset_queue', routing_key='superset.#'),
)
CELERY_CONFIG = CeleryConfig
I ran the commands for Gunicorn and celery, and the processes are running successfully.
In celery logs I am getting -
Traceback (most recent call last):
File "/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/celery/app/trace.py", line 453, in trace_task
R = retval = fun(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^
File "/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/superset/initialization/__init__.py", line 114, in __call__
return task_base.__call__(self, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/celery/app/trace.py", line 736, in __protected_call__
return self.run(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/superset/sql_lab.py", line 196, in get_sql_results
query = get_query(query_id=query_id)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/backoff/_sync.py", line 105, in retry
ret = target(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^
File "/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/superset/sql_lab.py", line 162, in get_query
raise SqlLabException("Failed at getting query") from ex
superset.sql_lab.SqlLabException: Failed at getting query
GitHub link: https://github.com/apache/superset/discussions/33920
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Unable to activate async querying in superset 5.0.0 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: Unable to activate async querying in superset 5.0.0
<!-- Answer -->
The error means the Celery worker can't find the Query record in the metadata DB when it tries to fetch it. This is almost always a timing or DB visibility issue, not a problem with your async flags or Celery config. Superset's async workflow commits the Query to the DB before the worker starts, but if the worker runs before the commit finishes (or before the row is visible due to MySQL replication lag or transaction isolation), you'll see this error—even if both processes use the same DB URI and can connect fine. The code retries a few times to handle this race, but if the Query is still missing, something is wrong with DB commit timing or visibility [source](https://github.com/apache/superset/blob/2e9939baf253e607a54722b1996baaf625e72133/superset/commands/sql_lab/execute.py).
Check your MySQL transaction isolation level (should be READ COMMITTED), make sure there’s no replication lag, and confirm that the web server logs show the Query being committed before the worker tries to fetch it. Also, Superset 5.0 removed GLOBAL_ASYNC_QUERIES_REDIS_CONFIG in favor of GLOBAL_ASYNC_QUERIES_CACHE_BACKEND and included new migrations—double-check that all migrations ran and your config matches the new requirements [source](https://github.com/apache/superset/issues/31842).
If you still see this after confirming the above, enable SQLAlchemy debug logging to see the exact timing of Query creation/commit and Celery fetch attempts. This will help pinpoint if it’s a race or a deeper DB/config issue.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
---
<sup>How did I do? [Good](https://app.dosu.dev/response-feedback/4bb6a049-3914-409e-8890-8597bd13e110?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/4bb6a049-3914-409e-8890-8597bd13e110?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/4bb6a049-3914-409e-8890-8597bd13e110?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/4bb6a049-3914-409e-8890-8597bd13e110?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/4bb6a049-3914-409e-8890-8597bd13e110?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/4bb6a049-3914-409e-8890-8597bd13e110?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/4bb6a049-3914-409e-8890-8597bd13e110?feedback_type=other)</sup> [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/33920)
GitHub link: https://github.com/apache/superset/discussions/33920#discussioncomment-13603975
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Unable to activate async querying in superset 5.0.0 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: Unable to activate async querying in superset 5.0.0
<!-- Answer -->
The error means the Celery worker can't find the Query record in the metadata DB when it tries to fetch it. This is almost always a timing or DB visibility issue, not a problem with your async flags or Celery config. Superset's async workflow commits the Query to the DB before the worker starts, but if the worker runs before the commit finishes (or before the row is visible due to MySQL replication lag or transaction isolation), you'll see this error—even if both processes use the same DB URI and can connect fine. The code retries a few times to handle this race, but if the Query is still missing, something is wrong with DB commit timing or visibility [source](https://github.com/apache/superset/blob/2e9939baf253e607a54722b1996baaf625e72133/superset/commands/sql_lab/execute.py).
Check your MySQL transaction isolation level (should be READ COMMITTED), make sure there’s no replication lag, and confirm that the web server logs show the Query being committed before the worker tries to fetch it. Also, Superset 5.0 removed GLOBAL_ASYNC_QUERIES_REDIS_CONFIG in favor of GLOBAL_ASYNC_QUERIES_CACHE_BACKEND and included new migrations—double-check that all migrations ran and your config matches the new requirements [source](https://github.com/apache/superset/issues/31842).
If you still see this after confirming the above, enable SQLAlchemy debug logging to see the exact timing of Query creation/commit and Celery fetch attempts. This will help pinpoint if it’s a race or a deeper DB/config issue.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=apache%2Fsuperset&message_id=4bb6a049-3914-409e-8890-8597bd13e110) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/33920#discussioncomment-13603975
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Unable to activate async querying in superset 5.0.0 [superset]
Posted by "Nimishbansal-16 (via GitHub)" <gi...@apache.org>.
GitHub user Nimishbansal-16 added a comment to the discussion: Unable to activate async querying in superset 5.0.0
@dosu Please help
GitHub link: https://github.com/apache/superset/discussions/33920#discussioncomment-13581487
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Unable to activate async querying in superset 5.0.0 [superset]
Posted by "Nimishbansal-16 (via GitHub)" <gi...@apache.org>.
GitHub user Nimishbansal-16 added a comment to the discussion: Unable to activate async querying in superset 5.0.0
@dosu?
GitHub link: https://github.com/apache/superset/discussions/33920#discussioncomment-13603966
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Unable to activate async querying in superset 5.0.0 [superset]
Posted by "Nimishbansal-16 (via GitHub)" <gi...@apache.org>.
GitHub user Nimishbansal-16 added a comment to the discussion: Unable to activate async querying in superset 5.0.0
@dosu
In SQLALCHEMY_DATABASE_URI, I have a mysql uri which is accessible by both.
Here is the full stack trace:
`[2025-06-26 06:24:53,544: INFO/ForkPoolWorker-2] Backing off get_query(...) for 0.1s (superset.sql_lab.SqlLabException: Failed at getting query)
[2025-06-26 06:24:53,544: ERROR/ForkPoolWorker-2] Query with id `103` could not be retrieved
Traceback (most recent call last):
File "/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/superset/sql_lab.py", line 160, in get_query
return db.session.query(Query).filter_by(id=query_id).one()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/sqlalchemy/orm/query.py", line 2870, in one
return self._iter().one()
^^^^^^^^^^^^^^^^^^
File "/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/sqlalchemy/engine/result.py", line 1522, in one
return self._only_one_row(
^^^^^^^^^^^^^^^^^^^
File "/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/sqlalchemy/engine/result.py", line 562, in _only_one_row
raise exc.NoResultFound(
sqlalchemy.exc.NoResultFound: No row was found when one was required
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/backoff/_sync.py", line 105, in retry
ret = target(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^
File "/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/superset/sql_lab.py", line 162, in get_query
raise SqlLabException("Failed at getting query") from ex
superset.sql_lab.SqlLabException: Failed at getting query
[2025-06-26 06:24:53,545: ERROR/ForkPoolWorker-2] Query 103: Sleeping for a sec before retrying...
Traceback (most recent call last):
File "/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/superset/sql_lab.py", line 160, in get_query
return db.session.query(Query).filter_by(id=query_id).one()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/sqlalchemy/orm/query.py", line 2870, in one
return self._iter().one()
^^^^^^^^^^^^^^^^^^
File "/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/sqlalchemy/engine/result.py", line 1522, in one
return self._only_one_row(
^^^^^^^^^^^^^^^^^^^
File "/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/sqlalchemy/engine/result.py", line 562, in _only_one_row
raise exc.NoResultFound(
sqlalchemy.exc.NoResultFound: No row was found when one was required
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/backoff/_sync.py", line 105, in retry
ret = target(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^
File "/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/superset/sql_lab.py", line 162, in get_query
raise SqlLabException("Failed at getting query") from ex
superset.sql_lab.SqlLabException: Failed at getting query
[2025-06-26 06:24:53,679: INFO/ForkPoolWorker-2] Backing off get_query(...) for 0.3s (superset.sql_lab.SqlLabException: Failed at getting query)
[2025-06-26 06:24:53,679: ERROR/ForkPoolWorker-2] Query with id `103` could not be retrieved
Traceback (most recent call last):
File "/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/superset/sql_lab.py", line 160, in get_query
return db.session.query(Query).filter_by(id=query_id).one()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/sqlalchemy/orm/query.py", line 2870, in one
return self._iter().one()
^^^^^^^^^^^^^^^^^^
File "/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/sqlalchemy/engine/result.py", line 1522, in one
return self._only_one_row(
^^^^^^^^^^^^^^^^^^^
File "/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/sqlalchemy/engine/result.py", line 562, in _only_one_row
raise exc.NoResultFound(
sqlalchemy.exc.NoResultFound: No row was found when one was required
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/backoff/_sync.py", line 105, in retry
ret = target(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^
File "/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/superset/sql_lab.py", line 162, in get_query
raise SqlLabException("Failed at getting query") from ex
superset.sql_lab.SqlLabException: Failed at getting query
[2025-06-26 06:24:53,680: ERROR/ForkPoolWorker-2] Query 103: Sleeping for a sec before retrying...
Traceback (most recent call last):
File "/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/superset/sql_lab.py", line 160, in get_query
return db.session.query(Query).filter_by(id=query_id).one()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/sqlalchemy/orm/query.py", line 2870, in one
return self._iter().one()
^^^^^^^^^^^^^^^^^^
File "/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/sqlalchemy/engine/result.py", line 1522, in one
return self._only_one_row(
^^^^^^^^^^^^^^^^^^^
File "/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/sqlalchemy/engine/result.py", line 562, in _only_one_row
raise exc.NoResultFound(
sqlalchemy.exc.NoResultFound: No row was found when one was required
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/backoff/_sync.py", line 105, in retry
ret = target(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^
File "/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/superset/sql_lab.py", line 162, in get_query
raise SqlLabException("Failed at getting query") from ex
superset.sql_lab.SqlLabException: Failed at getting query`
GitHub link: https://github.com/apache/superset/discussions/33920#discussioncomment-13592645
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Unable to activate async querying in superset 5.0.0 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: Unable to activate async querying in superset 5.0.0
<!-- Answer -->
The error SqlLabException: Failed at getting query almost always means the Celery worker can't access the shared metadata database. This isn't caused by async flags or Celery process issues, but by a config problem—usually the SQLALCHEMY_DATABASE_URI is different or inaccessible between your web server and Celery worker, or migrations are missing. Both processes must use the same superset_config.py and environment variables, and the metadata DB must not be SQLite (use PostgreSQL or MySQL) [source](https://github.com/apache/superset/blob/f802474b07bc7a2765e57fcd6612d2b4454f5c62/docs/docs/configuration/async-queries-celery.mdx).
Check that:
- Both web and worker use the same SQLALCHEMY_DATABASE_URI and can connect to the DB.
- All DB migrations are applied.
- The DB is reachable from both processes (try connecting from both environments).
- Asynchronous Query Execution is enabled in the database settings (Sources > Databases > Edit record) [source](https://github.com/apache/superset/issues/33218).
If you can share the full traceback (including the root cause exception), I can help interpret it further.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
---
<sup>How did I do? [Good](https://app.dosu.dev/response-feedback/417b45e3-62e7-475b-afad-3107d83c70a4?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/417b45e3-62e7-475b-afad-3107d83c70a4?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/417b45e3-62e7-475b-afad-3107d83c70a4?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/417b45e3-62e7-475b-afad-3107d83c70a4?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/417b45e3-62e7-475b-afad-3107d83c70a4?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/417b45e3-62e7-475b-afad-3107d83c70a4?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/417b45e3-62e7-475b-afad-3107d83c70a4?feedback_type=other)</sup> [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/33920)
GitHub link: https://github.com/apache/superset/discussions/33920#discussioncomment-13581513
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Unable to activate async querying in superset 5.0.0 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: Unable to activate async querying in superset 5.0.0
<!-- Answer -->
The error SqlLabException: Failed at getting query almost always means the Celery worker can't access the shared metadata database. This isn't caused by async flags or Celery process issues, but by a config problem—usually the SQLALCHEMY_DATABASE_URI is different or inaccessible between your web server and Celery worker, or migrations are missing. Both processes must use the same superset_config.py and environment variables, and the metadata DB must not be SQLite (use PostgreSQL or MySQL) [source](https://github.com/apache/superset/blob/f802474b07bc7a2765e57fcd6612d2b4454f5c62/docs/docs/configuration/async-queries-celery.mdx).
Check that:
- Both web and worker use the same SQLALCHEMY_DATABASE_URI and can connect to the DB.
- All DB migrations are applied.
- The DB is reachable from both processes (try connecting from both environments).
- Asynchronous Query Execution is enabled in the database settings (Sources > Databases > Edit record) [source](https://github.com/apache/superset/issues/33218).
If you can share the full traceback (including the root cause exception), I can help interpret it further.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=apache%2Fsuperset&message_id=417b45e3-62e7-475b-afad-3107d83c70a4) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/33920#discussioncomment-13581513
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org