Data and AI struggles

1,787 problems · 347 companies

Databases

Trouble with ClickHouse table

8 posts from 5 people5d activeFading, +0 this week

Posts per day

Posts per day8 posts, Sep 21 to Nov 11

The posts behind it

GitHub issuesClickHouse/ClickHouse · qoegaNov 2

SYSTEM DROP/PREWARM VECTOR SIMILARITY INDEX CACHE [FOR TABLE db.t] [INDEX idx]

## Problem With one or more tables, each with a `vector_similarity` (HNSW) index it is nice to cleanup each index cache separately. ## Requested 1. **Targeted drop:** `SYSTEM DROP VECTOR SIMILARITY INDEX CACHE [ON CLUSTER c] [FOR TABLE db.t [INDEX idx]]`. Evicts only that...

1 reactions
GitHub issuesClickHouse/ClickHouse · clickgapaiOct 24

MySQLDump format misparses `CREATE TABLE IF NOT EXISTS` table name as `IF`

...returns `IF` as the table name and `tryToExtractStructureFromCreateQuery` then fails to parse the remaining `NOT EXISTS t1 (...)`. Analysis details (evidence, affected locations, impact) Why we believe this is a bug: `readFirstCreateAndInsertQueries` (:433) ->...

GitHub issuesClickHouse/ClickHouse · filimonovOct 23

`SYSTEM RESTORE REPLICA` on a second replica over-bumps the table `metadata` znode version; every later `ALTER` fails with `CANNOT_ASSIGN_ALTER` (26.3+)

...and a server restart do not help. The table serves reads and writes, only `ALTER` is broken. Cause: `restoreMetadataInZooKeeper` raises the `stat.version` of ` /metadata` **by** the max `metadata_version.txt` of the local parts (M), not **to** it. The first restored replica...

1 reactions5 replies
GitHub issuesClickHouse/ClickHouse · leshikusOct 23

`BACKUP` to `File()` on a case-insensitive filesystem: fail on names that differ only in case instead of dropping one silently, as `CREATE TABLE` already does

Detect two names that collide on a case-insensitive filesystem when writing a backup to `File()`, and fail the `BACKUP` (or encode the names so both survive). That lets a `File()` backup taken on macOS restore every table. ClickHouse 26.4.3.37 and master, macOS on APFS...

2 replies
GitHub issuesClickHouse/ClickHouse · clickgapaiSep 22

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...

GitHub issuesClickHouse/ClickHouse · clickgapaiSep 21

Distributed-destination INSERT SELECT still forwards the plain table function

### Describe what's wrong - `INSERT INTO SELECT * FROM url(...)` inserts the source data once per destination shard - Triggered with `parallel_replicas_for_cluster_engines = 1`, `enable_parallel_replicas = 1`, `cluster_for_parallel_replicas` set and...

GitHub issuesClickHouse/ClickHouse · alexey-milovidovSep 21

Wrong results: `variantElement` over a `Merge` table returns `NULL` unless it is in the top-level projection

...`multiIf` into a subquery projection and filtering on its alias in the outer query is a workaround and produces the documented rows. Related: https://github.com/ClickHouse/ClickHouse/issues/121166

GitHub issuesClickHouse/ClickHouse · qoegaSep 21

clickhouse local: table/dictionary names longer than NAME_MAX raise std::filesystem_error (code 1001) instead of UNKNOWN_TABLE

In `clickhouse local`, any query naming a table or dictionary with more than 255 bytes in its name fails with `std::filesystem_error` (`Code 1001 (STD_EXCEPTION)`) instead of a normal `UNKNOWN_TABLE` / "Dictionary not found". The default database in `clickhouse local` overlays...

2 replies

Companies and products named

8 posts
6 posts
1 post
About this problem

Evidence

8 posts from 5 people in 1 place, about 1 a week over 43 days. Mostly on ClickHouse/ClickHouse. Tools named alongside: GitHub, MySQL.

Frustration Frustration 0 of 3· Seen on GitHub issues

How it was grouped

Posts about ClickHouse with no known issue, sharing the word "table". First post Sep 21, 2026, latest Nov 2, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method

Other ClickHouse problems

ClickHouse upgrades break working setups

31 posts from 20 people on GitHub issues.

ClickHouse users keep filing bugs

Top post: "Tighten seccomp policy for optional kernel interfaces", one of 19 posts from 8 people on GitHub issues.

Trouble with ClickHouse column

Top post: "MaterializedPostgreSQL: reading a Nullable column's .null subcolumn (x IS NULL, count(x)) fails with", one of 15 posts from 9 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

8 posts from 1 person on GitHub issues. Unverified.

Trouble with ClickHouse tables

Top post: "Paimon: resolve columns by field id, so tables with renamed or re-added columns are readable", one of 7 posts from 6 people on GitHub issues.

Trouble with ClickHouse join

Top post: "Explicit grace_hash now spills at max_bytes_ratio_before_external_join = 0.5 although the build side fits in", one of 5 posts from 4 people on GitHub issues.

ClickHouse error messages are cryptic

5 posts from 3 people on GitHub issues.

Trouble with ClickHouse read

Top post: "ORC: a corrupt PostScript `metadata_length` makes ORC predicate pushdown read `stripe_stats` out of bounds,", one of 4 posts from 4 people on GitHub issues.

Trouble with ClickHouse database

Top post: "`DROP NAMED COLLECTION` succeeds while a database uses the collection, and the server then fails to start", one of 4 posts from 2 people on GitHub issues.

Trouble with ClickHouse query

Top post: "Memory tracker counts jemalloc's freed pages as used, so a heavy query started right after another spills to", one of 4 posts from 3 people on GitHub issues.

ClickHouse rate limits and usage caps block work

3 posts from 3 people on GitHub issues.

History

Momentum went from steady to fading.

Nov 9, 2026

Momentum went from fading to steady.

Nov 6, 2026

Momentum went from steady to fading.

Oct 31, 2026

Momentum went from rising to steady.

Oct 30, 2026

Corroborated: 3 or more posts from 2 or more people or places.

Oct 28, 2026

Momentum went from fading to rising.

Oct 28, 2026

Back to unverified: fewer than 3 posts from 2 people or places.

Oct 18, 2026

Momentum went from new to fading.

Sep 28, 2026

First seen with 4 posts; the top post now: "`SYSTEM RESTORE REPLICA` on a second replica over-bumps the table `metadata` znode version; every later".

Sep 27, 2026