GitHub user dosubot[bot] added a comment to the discussion: Superset is not able to load the result from hydrolix
<!-- Answer --> The critical difference is visible in the error from your first message — when the query goes through Superset, it arrives at Hydrolix with these **appended SETTINGS**: ``` SETTINGS hdx_query_pool_name = 'query-peer', hdx_query_max_memory_usage = 40802189312, hdx_query_timerange_required = TRUE, hdx_query_max_timerange_sec = 5356800, hdx_query_max_execution_time = 120, ... ``` **Superset itself does NOT add these SETTINGS** — they don't exist anywhere in the Superset codebase [[1]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/db_engine_specs/clickhouse.py). These are being injected somewhere in your environment, most likely by one of: 1. **Your `SQL_QUERY_MUTATOR` in `superset_config.py`** — This is a custom hook that can modify every query before execution [[2]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/models/core.py#L634-L652). Check if you have something like: ```python SQL_QUERY_MUTATOR = some_function_that_appends_hydrolix_settings ``` 2. **The `clickhouse-connect` driver's connection parameters** — Check your database connection's "Extra" JSON field or engine parameters. The newer driver version (>=0.13.0) may handle connection-level settings differently, causing Hydrolix to apply pool-level query settings (like `hdx_query_timerange_required = TRUE`) that weren't applied with the older driver. 3. **Hydrolix proxy/server-side configuration** — Hydrolix might be applying these SETTINGS at the query pool level based on the connecting user or client identifier. The newer `clickhouse-connect` sends `product_name = "superset/{VERSION}"` [[3]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/db_engine_specs/clickhouse.py#L248-L251), which Hydrolix could use to route queries to a pool that enforces `hdx_query_timerange_required = TRUE`. **The fix**: The `hdx_query_timerange_required = TRUE` setting is what's causing the rejection. You need to either: - Find where these SETTINGS are being injected and remove/modify `hdx_query_timerange_required` - Or configure your Hydrolix query pool to not enforce this setting for Superset connections When you run the query directly in Hydrolix, it likely goes through a different query pool that doesn't enforce `hdx_query_timerange_required`. Could you check your Hydrolix query pool configuration and your Superset `superset_config.py` for a `SQL_QUERY_MUTATOR`? <!-- 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=7344c03a-b252-4706-9fb9-e2f65343a428) [](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-17424906 ---- 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]
