Open ericpgreen2 opened 1 month ago
I think this was introduced in this PR : https://github.com/rilldata/rill/pull/5103
The max_execution_time
settings is added directly by underlying driver.
The issue is that clickhouse playground is very restrictive and the readonly=1
was sort of a workaround. Now we may be able to circumnavigate around this issue too but longer term but longer term we need to think if we should really continue to support clickhouse playground or not.
cc : @nishantmonu51
IMO it's important to support ClickHouse Playground for demos. At least for dashboards. It's understandable if modeling (i.e. writebacks) is not supported.
Here's my ClickHouse connector YAML:
I've created the following dashboard:
The dashboard is blank with the following error: "clickhouse [execute]:: 500 code: Code: 164. DB::Exception: Cannot modify 'max_execution_time' setting in readonly mode. (READONLY) (version 24.6.1.2672 (official build))\n"