GitHub user dosubot[bot] added a comment to the discussion: Superset is not able to load the result from hydrolix
<!-- Answer --> Thanks for the additional context. The key change between Superset v5 and v6.1.0 for ClickHouse was [PR #38280](https://github.com/apache/superset/pull/38280), which bumped the minimum `clickhouse-connect` version to `>=0.13.0` and removed the `_mutate_label` workaround. However, that PR did **not** change how time range filters or datetime literals are generated — it only removed the column alias hashing behavior. So the core query generation (including `toDateTime('...')` wrapping) hasn't changed between v5 and v6. What likely changed is how the **driver itself sends the query to Hydrolix**. Newer versions of `clickhouse-connect` may send queries differently (e.g., different protocol settings, different `SETTINGS` injection behavior) which could affect how Hydrolix's validator parses the time range filter. Here's what I'd suggest investigating: 1. **Check if `clickhouse-connect` >=0.13.0 changed how `SETTINGS` are appended** — The error shows `SETTINGS hdx_query_timerange_required = TRUE` being appended to the query. If the driver now sends the query + settings in a way that Hydrolix's validator parses differently, that could explain why the time range is no longer recognized. 2. **Test with the raw query** — Run the exact SQL (without the `SETTINGS` line) directly against Hydrolix via `clickhouse-client` or another tool to confirm whether Hydrolix can parse `toDateTime('...')` as a valid time range filter. 3. **Check Hydrolix compatibility with newer clickhouse-connect** — This may be a known issue on the Hydrolix side. Their query validator (`hdx_query_timerange_required`) may need an update to handle queries sent by newer driver versions. 4. **Workaround: Pin clickhouse-connect** — If you need an immediate fix, you could try pinning `clickhouse-connect` to a version just below what breaks (though this conflicts with Superset 6.1.0's requirement of `>=0.13.0`). Alternatively, check if Hydrolix allows disabling `hdx_query_timerange_required` in your query pool configuration. The root issue appears to be that Hydrolix's time-range validator isn't recognizing the filter in queries sent via the newer driver version. This is likely a Hydrolix-side compatibility issue rather than a Superset regression — the SQL itself is identical, but the transport/protocol behavior of the driver may have changed. <!-- 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=80b52aca-393b-401d-9e7b-d0e33e512d12) [](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/41395#discussioncomment-17424758 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
