Trouble with ClickHouse value
4 posts from 2 people3d activeFading, +0 this week
Posts per day
The posts behind it
Docs: h3GetResolution incorrectly says invalid indexes return a random value
### Describe the issue The manual H3 function reference says that `h3GetResolution` returns a random value when the input is not a valid H3 index: https://github.com/ClickHouse/ClickHouse/blob/master/docs/reference/functions/regular-functions/geo/h3.mdx#L69 The current...
Row policy with DateTime64/Time64 query parameter re-parses to wrong value
### Describe what's wrong - A row policy created with a `DateTime64` or `Time64` query parameter does not keep the value it was created with. - Trigger: `CREATE ROW POLICY ... USING ts Analysis details (evidence, affected locations, impact) Why we believe this is a bug:...
Stack-overflow SIGSEGV on SELECT of deeply nested constant `Dynamic` value
### Describe what's wrong - A plain `SELECT` of a deeply nested constant `Dynamic` value crashes the server with a stack-overflow SIGSEGV at default settings. - Trigger: `finalizeAggregation` of a binary `AggregateFunction(any, Dynamic)` state with 4000 levels of...
Hashing a deeply nested `Dynamic`/`JSON` value crashes the server with SIGSEGV
### Describe what's wrong - `sipHash64`, `cityHash64`, `xxHash64` and `murmurHash3_64` over a deeply nested `Dynamic`/`JSON` value exhaust the stack and crash the server. - Trigger: hash a `Dynamic` value with thousands of nested `Object` levels, e.g. built via...
Companies and products named
About this problem
Evidence
4 posts from 2 people in 1 place, about 1 a week over 22 days. Mostly on ClickHouse/ClickHouse. Tools named alongside: GitHub.
Frustration Frustration 0 of 3· Seen on GitHub issues
How it was grouped
Posts about ClickHouse with no known issue, sharing the word "value". First post Oct 5, 2026, latest Oct 26, 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 default
Top post: "`merge('', regexp)` still resolves against the shard's default database", 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.
History