dosubot[bot] commented on issue #37114: URL: https://github.com/apache/superset/issues/37114#issuecomment-3748511129
<!-- Answer --> You're correct—[PR #35419](https://github.com/apache/superset/pull/35419) only normalizes and sanitizes the `where` and `having` clauses before cache key generation. It does not address `orderby.sqlExpression`, so cache key mismatches due to formatting differences or Jinja rendering in `orderby.sqlExpression` remain unresolved. This is a known gap and can still cause cache misses and async query errors if, for example, newlines or template output differ between the web UI and worker processes. There isn't an official fix for this yet—workarounds are still needed for charts that rely on custom SQL in order by clauses. If you need more details on possible workarounds or want to track this gap, let me know! <!-- 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/40f5d22e-d5fe-4455-86e5-5d4a0adb569c?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/40f5d22e-d5fe-4455-86e5-5d4a0adb569c?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/40f5d22e-d5fe-4455-86e5-5d4a0adb569c?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/40f5d22e-d5fe-4455-86e5-5d4a0adb569c?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/40f5d22e-d5fe-4455-86e5-5d4a0adb569c?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/40f5d22e-d5fe-4455-86e5-5d4a0adb569c?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/40f5d22e-d5fe-4455-86e5-5d4a0adb569c?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=You%27re%20correct%E2%80%94%5BPR%20%2335419%5D%28https%3A//github.com/apache/superset/pull/35419%29%20only%20normalizes%20and%20sanitizes%20the%20%60where%60%20and%20%60having%60%20clauses%20before%20cache%20key%20generation.%20It%20does%20not%20address%20%60orderby.sqlExpression%60%2C%20so%20cache%20key%20mismatches%20due%20to%20formatting%20differences%20or%20Jinja%20rendering%20in%20%60orderby.sqlExpression%60%20remain%20unresolved.%20This%20is%20a%20known%20gap%20and%20can%20still%20cause%20cache%20misses%20and%20async%20query%20errors%20if%2C%20for%20example%2C%20newlines%20or%20template%20output%20differ%20between%20the%20web%20UI%20and%20worker%20processes.%20There%20isn%27t%20an%20official%20fix%20for%20this%20yet%E2%80%94workarounds%20are% 20still%20needed%20for%20charts%20that%20rely%20on%20custom%20SQL%20in%20order%20by%20clauses.%20%0A%0AIf%20you%20need%20more%20details%20on%20possible%20workarounds%20or%20want%20to%20track%20this%20gap%2C%20let%20me%20know%21) [](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/issues/37114) -- 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]
