Trouble with ClickHouse default
5 posts from 4 people4d activeFading, +0 this week
Posts per day
The posts behind it
`merge('', regexp)` still resolves against the shard's default database
### Describe what's wrong - `merge('', regexp)` used inside a distributed `IN`/`JOIN` subquery still resolves `''` on each shard instead of the initiator. - Triggered by `remote()`/`Distributed` queries with `prefer_localhost_replica = 0` calling `merge('', regexp)` in a...
"Sync columns from source" fails on ClickHouse tables with ALIAS, MATERIALIZED or DEFAULT columns
...extra (` =1.7.2` and CI runs 1.7.2, so on 7.0 every route hits it. - Workaround: `PUT /api/v1/dataset/ /refresh` refreshes the columns from the source and works. - cc @joe-clickhouse, @hughhhh (#24248), @rusackas (#40944) ### Checklist - [x] I have searched Superset docs and...
INSERT SELECT from fileCluster/urlCluster fails to fill DEFAULT columns
### Describe what's wrong - INSERT INTO d SELECT * FROM fileCluster(...) or urlCluster(...) fails instead of inserting. - Triggered when the source files lack columns that have DEFAULT expressions on the destination table. - Expected the DEFAULT expressions to be filled in like...
Default value instead of exception in insert...select
...response_ ### Related issues and pull requests _No response_ ### Additional context As a workaround I found that somehow setting `insert_null_as_default` to 0, which defaults to 1, fixes the issue
A database `SETTINGS unknown_name = DEFAULT` is accepted and stored
### Describe what's wrong `CREATE DATABASE ... SETTINGS` rejects an unknown setting written as `name = value` (`UNKNOWN_SETTING`), but accepts the same name written as `name = DEFAULT`, and stores it in the database's definition, where it stays after a restart. A typo in a reset...
Companies and products named
About this problem
Evidence
5 posts from 4 people in 2 places, about 1 a week over 32 days. Mostly on ClickHouse/ClickHouse, apache/superset. Tools named alongside: GitHub, Apache Superset, Docker, Slack.
Frustration Frustration 0 of 3· Seen on GitHub issues
How it was grouped
Posts about ClickHouse with no known issue, sharing the word "default". First post Oct 13, 2026, latest Nov 13, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method
Other ClickHouse problems
ClickHouse upgrades break working setups
37 posts from 21 people on GitHub issues.
ClickHouse users keep filing bugs
Top post: "Tighten seccomp policy for optional kernel interfaces", one of 22 posts from 10 people on GitHub issues.
Trouble with ClickHouse column
Top post: "Top-K reads with a `minmax` index on the sort column: read the granules with the best bounds first", one of 17 posts from 10 people on GitHub issues.
ClickHouse costs outgrow the value it gives
11 posts from 3 people on GitHub issues.
Experiments on ClickHouse are hard to reproduce and track
11 posts from 2 people on GitHub issues.
Trouble with ClickHouse table
Top post: "`SYSTEM RESTORE REPLICA` on a second replica over-bumps the table `metadata` znode version; every later", one of 9 posts from 5 people on GitHub issues.
Trouble with ClickHouse join
Top post: "JOIN runtime filter pruning drops rows for CAST(UInt8 AS Bool) probe key", one of 7 posts from 5 people on GitHub issues.
Trouble with ClickHouse read
Top post: "Bucketed `Map` serialization loses the key order in Compact parts written with", one of 6 posts from 6 people on GitHub issues.
ClickHouse error messages are cryptic
6 posts from 3 people on GitHub issues.
Trouble with ClickHouse tables
Top post: "Paimon: resolve columns by field id, so tables with renamed or re-added columns are readable", one of 5 posts from 4 people on GitHub issues.
Trouble with ClickHouse index
Top post: "Text index: exact hasPhrase on Array columns with a position increment gap", one of 4 posts from 2 people on GitHub issues.
ClickHouse rate limits and usage caps block work
4 posts from 3 people on GitHub issues.
History