GitHub user dosubot[bot] added a comment to the discussion: Superset is not able to load the result from hydrolix
<!-- Answer --> Based on my research, the key change that's likely causing Hydrolix to reject your queries is **how the newer `clickhouse-connect` driver sends the query over HTTP** — specifically the `FORMAT Native` clause appended to the end of the query. Looking at the error you posted earlier, the query Hydrolix receives ends with: ``` ...LIMIT 10000 SETTINGS hdx_query_timerange_required = TRUE, ... FORMAT Native ``` Here's what's happening: **The `clickhouse-connect` driver (not Superset) appends `FORMAT Native`** to your query before sending it over the HTTP interface [[1]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/db_engine_specs/clickhouse.py). Superset itself does not add this — it's an internal behavior of the driver to request results in ClickHouse's binary Native format. **What likely changed between the old and new driver versions:** 1. **FORMAT clause positioning** — In older versions (0.5.x/0.6.x), the driver may have sent the format specification differently (e.g., via HTTP parameters, or using a different format like JSON/TabSeparated). In 0.13.0+, it appears to append `FORMAT Native` directly to the SQL text. 2. **SETTINGS + FORMAT interaction** — Your `SQL_QUERY_MUTATOR` appends `SETTINGS ...` to the query, and then the driver appends `FORMAT Native` after that. The combined query structure may be confusing Hydrolix's time-range parser. **Hydrolix's validator likely parses the raw SQL text to find time range filters, and the `FORMAT Native` suffix (or the way SETTINGS are positioned relative to it) may be breaking that parsing in the newer driver.** 3. **The version bump was for a different reason** — PR #38280 bumped the version to remove a column-alias hashing workaround (`_mutate_label`), not because of any query formatting changes [[2]](https://github.com/apache/superset/pull/38280). The `FORMAT Native` behavior change is a side effect. **To confirm this theory**, you can: - Enable debug logging on the `clickhouse-connect` driver to see the exact raw HTTP request being sent - Or use a network proxy to capture the actual query text sent to Hydrolix's HTTP endpoint **The root cause** is that Hydrolix's time-range validator cannot parse the time filter when the query ends with `SETTINGS ... FORMAT Native`. This is ultimately a Hydrolix compatibility issue with how newer `clickhouse-connect` versions structure HTTP requests — they need to update their SQL parser to handle this format. <!-- 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=8714f6dd-a0eb-4054-9544-84b714ef6fee) [](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-17425476 ---- 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]
