GitHub user dosubot[bot] added a comment to the discussion: Superset is not
able to load the result from hydrolix
<!-- Answer -->
Thanks for sharing — this confirms the issue. Your `SQL_QUERY_MUTATOR` is
explicitly setting `hdx_query_timerange_required = True` in the
`get_settings()` function:
```python
settings = {
"hdx_query_pool_name": "query-peer",
"hdx_query_max_memory_usage": 38 * BINARY_GIGA,
"hdx_query_timerange_required": True, # <-- This is the culprit
"hdx_query_max_timerange_sec": 62 * SECONDS_PER_DAY,
"hdx_query_max_execution_time": 120,
}
```
So the flow is: Superset generates the query with a valid `WHERE "timestamp" >=
toDateTime('...')` filter → your mutator appends `SETTINGS
hdx_query_timerange_required = TRUE` → Hydrolix's validator **fails to
recognize** the time filter format and rejects the query.
The query itself is correct, but **Hydrolix's server-side validator doesn't
recognize `toDateTime('...')` wrapping as a valid time range filter**. This
likely worked in v5 because:
- The older `clickhouse-connect` driver may have sent the query differently
(e.g., different quoting or format)
- Or Hydrolix's server version at the time had different validation logic
**Your options to fix this:**
1. **Quick fix — set `hdx_query_timerange_required` to `False`** in your
default settings:
```python
"hdx_query_timerange_required": False,
```
This bypasses the server-side validation entirely. The time filter is still
in your query, so you're not losing any safety.
2. **Make it mutable per-query** — Since `hdx_query_timerange_required` is
already in your `mutable_settings` set, users can override it by adding
`SETTINGS hdx_query_timerange_required = FALSE` in their query SQL before the
mutator processes it.
3. **Contact Hydrolix support** — Ask them why their validator (version
24.8.6.1) doesn't recognize `"timestamp" >= toDateTime('2026-06-23 14:02:34')`
as a valid time range filter. This may be a bug on their side, especially if it
worked with their previous server version.
4. **Custom time filter format** — If Hydrolix requires bare string comparisons
(without `toDateTime()`), you could create a custom ClickHouse engine spec that
overrides `convert_dttm()` to output `'2026-06-23 14:02:34'` instead of
`toDateTime('2026-06-23 14:02:34')`. However, this would affect all queries,
not just Hydrolix-validated ones.
The simplest immediate fix is option 1 — set `hdx_query_timerange_required` to
`False` since your queries already include time range filters by design.
<!-- 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=c413dac1-a6cd-4ed7-b0eb-a45f7ccf3cb0)
[](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-17424932
----
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]
