dosubot[bot] commented on issue #35263:
URL: https://github.com/apache/superset/issues/35263#issuecomment-3327318247

   <!-- Answer -->
   Yes, there are several highly relevant issues and PRs in the Superset 
repository that match your scenario:
   
   - Issue [#33773](https://github.com/apache/superset/issues/33773) describes 
the same bug: Drill to Detail and Drill by do not work properly on charts 
powered by Jinja templating because drill queries lack the full 
dashboard/global filter context, causing Jinja SQL to render with missing 
values. The suggested workaround is to make your Jinja SQL more robust with 
if/else blocks, but this doesn't fully solve the context propagation problem.
   - PRs [#34694](https://github.com/apache/superset/pull/34694) and 
[#34620](https://github.com/apache/superset/pull/34620) fix related issues 
where Drill to Detail returned all or no rows due to filter column name 
mismatches, by mapping axis label filters to original column names before 
executing the drill query. These help with filter propagation but do not 
address the Jinja context gap.
   - PR [#34319](https://github.com/apache/superset/pull/34319) enabled Drill 
to Detail and Drill By in embedded mode and with DASHBOARD_RBAC, but does not 
address Jinja templating or filter propagation in drill queries.
   
   The core architectural limitation—drill queries not merging dashboard/native 
filter context for Jinja-based datasets—remains as of the latest releases. You 
can track the above issue and PRs for updates or further discussion.
   
   
   <!-- 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/31c3c24a-edd2-4bc8-b9b0-2dacf9ac5794?feedback_type=great_response)
 | 
[Irrelevant](https://app.dosu.dev/response-feedback/31c3c24a-edd2-4bc8-b9b0-2dacf9ac5794?feedback_type=irrelevant_answer)
 | 
[Incorrect](https://app.dosu.dev/response-feedback/31c3c24a-edd2-4bc8-b9b0-2dacf9ac5794?feedback_type=incorrect_sources)
 | 
[Verbose](https://app.dosu.dev/response-feedback/31c3c24a-edd2-4bc8-b9b0-2dacf9ac5794?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/31c3c24a-edd2-4bc8-b9b0-2dacf9ac5794?feedback_type=hallucination)
 | [Report 
🐛](https://app.dosu.dev/response-feedback/31c3c24a-edd2-4bc8-b9b0-2dacf9ac5794?feedback_type=bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/31c3c24a-edd2-4bc8-b9b0-2dacf9ac5794?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat
 with 
Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=githu
 b)&nbsp;[![Join 
Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share
 on 
X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/35263)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to