You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "dosubot[bot] (via GitHub)" <gi...@apache.org> on 2026/05/02 02:58:35 UTC
Re: [D] warm_up_cache API doesn't apply filters when the dataset uses the filter_values Jinja macro [superset]
GitHub user dosubot[bot] edited a comment on the discussion: warm_up_cache API doesn't apply filters when the dataset uses the filter_values Jinja macro
<!-- Greeting -->
Hi @pandax08! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team.
<!-- Answer -->
This is a known limitation in the current implementation of the /api/v1/dataset/warm_up_cache endpoint. The extra_filters you send are only merged into the chart's form_data—and thus made available to the filter_values Jinja macro—if a dashboard_id is provided. If dashboard_id is missing or not handled as expected, extra_filters are ignored, which causes filter_values to always return an empty list in your virtual dataset SQL. This explains why your filters are not applied during cache warming, even though they work in other contexts.
This behavior is likely an unintentional bug or omission in the cache warming logic. The code path for warm_up_cache only attaches extra_filters to form_data when dashboard_id is present, and does not merge them otherwise, so the Jinja context never sees your filters. No recent pull requests address this issue yet, so it's not fixed in the latest versions [[source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/commands/chart/warm_up_cache.py)].
As a workaround, always provide a valid dashboard_id in your API call, and ensure that the charts you want to warm up are associated with that dashboard. This should allow extra_filters to be merged and passed to filter_values as expected. If you need to warm up cache for charts not tied to a dashboard, you may need to manually trigger cache warming for each chart with the appropriate form_data, or consider patching the logic to always merge extra_filters regardless of dashboard context.
Let me know if you need more details on the workaround or want to discuss alternative strategies!
<!-- 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=c0d48b82-b2ad-4aa7-bcc6-865ee89edc96) [](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/34979#discussioncomment-14279806
----
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