r/ApacheIceberg

▲ 19 r/ApacheIceberg+1 crossposts

Delete types in Apache Iceberg v3

Deletion Vectors are among the major improvements introduced in Apache Iceberg v3. Instead of creating separate position delete files, a deletion vector stores a compact bitmap for a single data file that marks which row positions have been deleted.

This approach improves performance and preserves more useful statistics for data files. It also makes it easier to compare previous and current deletes, simplifying the processing of a table’s row-level changes as a stream.

u/Low_Brilliant_2597 — 3 days ago

I think we are overpricing models and underpricing the data layer

I’ve been thinking about this after seeing more AI systems move from demos into actual production.

A lot of the public conversation is still around models: which one reasons better, which one is cheaper, which one has a longer context window, which one is faster.

That all matters. I’m not trying to dismiss it.

But the failures I keep noticing are often less about the model and more about the data it is working with.

The answer is wrong because the context was stale.

The agent made a bad decision because it pulled from the wrong source.

The retrieval worked in a clean test, but started failing once real-world issues showed up: permissions, messy metadata, stale documents, duplicated records.

The system said it had “real-time” data, but some important field was still coming from a batch job.

In those cases, a better model might help a little, but it does not fix the underlying problem. The model is still reasoning over a bad view of the world.

I used to think of the data layer as the boring plumbing underneath AI apps. Necessary, but not the main story.

Now I think that view was too simplistic.

Maybe the real value in production AI is not just better reasoning, but better context: data that is fresh, trusted, governed, searchable, and cheap enough to use often.

reddit.com
u/ethanchen20250322 — 9 days ago