Data and AI struggles

1,483 problems · 320 companies

Data engineering

DuckDB schema changes break downstream pipelines

2 posts from 2 people2d activeSteady, +1 this weekunverified

Posts per day

Posts per day2 posts, Sep 6 to Nov 2

The posts behind it

GitHub issuesduckdb/duckdb · OneCyrusOct 30

Use VARIANT automatically for inferred JSON objects and complex columns

...objects, `MAP(...)` for varying keys, and `JSON` for heterogeneous values. - There is no way to ask the reader for `VARIANT` output today. Declaring the column explicitly as `VARIANT` does not work either: ### Scope / considerations - Applies to `read_json`, `read_json_auto`,...

1 replies
GitHub issuesduckdb/duckdb · treillySep 6

duckdb 1.4.4 (node-duckdb): complete WAL fails to replay with "Conflict on tuple deletion" on reopen

## Environment - duckdb 1.4.4 via node-duckdb (node-v20.20.2, Linux WSL2) - single-process embedded use - `.duckdb` file (536,576 B) + `.duckdb.wal` file (12,873 B) ## Symptoms A specific `.duckdb` + `.wal` pair fails **deterministically** (3/3 reproducible in a fresh process)...

1 replies

Companies and products named

2 posts
About this problem

Evidence

2 posts from 2 people in 1 place, about 1 a week over 55 days. Mostly on duckdb/duckdb.

Frustration Frustration 0 of 3· Seen on GitHub issues

How it was grouped

Posts that state a pain and match the "schema-drift" rule about DuckDB. First post Sep 6, 2026, latest Oct 30, 2026. Unverified: fewer than 3 posts, or one person or place only. Method

The same problem elsewhere

Upstream schema changes break downstream pipelines

7 posts from 7 people on GitHub issues, Reddit.

Databricks schema changes break downstream pipelines

3 posts from 3 people on GitHub issues, Reddit.

Apache Iceberg schema changes break downstream pipelines

2 posts from 2 people on GitHub issues. Unverified.

Airbyte schema changes break downstream pipelines

2 posts from 2 people on GitHub issues. Unverified.

Apache Flink schema changes break downstream pipelines

2 posts from 2 people on GitHub issues. Unverified.

Other DuckDB problems

DuckDB upgrades break working setups

36 posts from 27 people on GitHub issues.

Trouble with DuckDB internal

Top post: "duckdb 2.0.0 fails to launch on BE: `INTERNAL Error: The time zone data is corrupt`", one of 14 posts from 7 people on GitHub issues.

Experiments on DuckDB are hard to reproduce and track

6 posts from 4 people on GitHub issues.

Trouble with DuckDB cast

Top post: "TRY_CAST of an empty BLOB to BIT escapes a non-fallible __cast and invalidates the database", one of 7 posts from 6 people on GitHub issues.

Trouble with DuckDB returns

Top post: "Comparison simplification returns an incorrect result when a narrowing `DECIMAL` cast is used", one of 9 posts from 9 people on GitHub issues.

DuckDB error messages are cryptic

11 posts from 7 people on GitHub issues.

Trouble with DuckDB join

Top post: "Segfault in `dense_rank() OVER ()` over a RIGHT_ANTI hash join that returns its unmatched rows", one of 9 posts from 8 people on GitHub issues.

Trouble with DuckDB column

Top post: "2.0 alpha: comparing a CASE/split_part result to a constant fails with BindBuiltinScalarFunction did not", one of 7 posts from 5 people on GitHub issues.

Trouble with DuckDB null

Top post: "DuckDB: `HAVING` of `(φ IS TRUE) OR NOT (φ IS TRUE) AND …` is empty for a NULL `φ`, but the same boolean as", one of 6 posts from 6 people on GitHub issues.

Trouble with DuckDB values

Top post: "ManualVuln37 Unbounded Recursion in EncodeVariantValue Causes Stack Overflow via variant_comparator on Deeply", one of 6 posts from 6 people on GitHub issues.

Trouble with DuckDB parquet

Top post: "External file cache range metadata grows for deleted local Parquet files in v1.5.6 despite buffer eviction", one of 5 posts from 5 people on GitHub issues.

DuckDB costs outgrow the value it gives

4 posts from 4 people on GitHub issues.

History

First seen with 2 posts.

Nov 2, 2026