Problemsby IbisTrouble with ClickHouse read
Databases4 posts from 3 people3d active+00 posts in the last 7 days, 1 the 7 days before (fading)
Posts per day
The posts behind it
4, newest firstStatic YTsaurus read with max_streams = 0 fails with LOGICAL_ERROR### Describe what's wrong - Reading a static YTsaurus table with `max_streams = 0` throws `Cannot resize an empty Pipe`. - Reproduced via the `ytsaurus` table function, the `YTsaurus` table engine, and a `HASHED` dictionary source. - With `max_streams = 1` the same read returns...ClickHouse/ClickHouse · clickgapaiOpen ↗ORC: a corrupt PostScript `metadata_length` makes ORC predicate pushdown read `stripe_stats` out of bounds — server SEGV on release (`startNextStripe`)...protobuf parseable but short of a `stripe_stats` entry for some stripe (a value that fails to parse gives a clean `Code: 1001 orc::ParseError`). The file above (two stripes, `metadata_length` + 2) reproduces 5/5. ### Expected behavior A clean data error...ClickHouse/ClickHouse · PedroTadim3 repliesOpen ↗Cache dictionary table read fabricates a DEFAULT row for a deleted source key### Describe what's wrong - Reading a `cache`, `complex_key_cache` or `ssd_cache` dictionary as a table can return a row for a key that exists nowhere. - Trigger: a cached cell expires per `LIFETIME` and the key has since been deleted from the source. - Expected: the row is...ClickHouse/ClickHouse · clickgapaiOpen ↗parseQueryToJSON writes a large Float64 literal that formatQueryFromJSON cannot read back (integer overflow in Poco JSON parser)`parseQueryToJSON` writes a large `Float64` literal in positional notation (no `.`, no `e`), and `formatQueryFromJSON` refuses its own writer's output because the JSON parser (Poco) classifies a number without `.`/`e` as an integer and fails when it does not fit 64 bits. ###...ClickHouse/ClickHouse · qoegaOpen ↗
Companies and products named
About this problem
Evidence
4 posts from 3 people in 1 place, about 1 a week over 21 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 "read". First post Sep 22, 2026, latest Oct 12, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method
Other ClickHouse problems
ClickHouse upgrades break working setupsTrouble with ClickHouse jsonClickHouse costs outgrow the value it givesClickHouse users keep filing bugsTrouble with ClickHouse columnTrouble with ClickHouse rowsExperiments on ClickHouse are hard to reproduce and trackTrouble with ClickHouse joinTrouble with ClickHouse nameClickHouse error messages are crypticTrouble with ClickHouse constantTrouble with ClickHouse slower
History
steady to fading
fading to steady
steady to fading
Trouble with ClickHouse read (3 posts)