Recent submissions

Comment · 4 months ago
TL;DR: IceStream keeps a secondary index of iceberg data on object store to enable efficient conversions from equality deletes to positional deletes in a horizontally scalable manner. After benchmarking this a bit you can see order of magnitude improvements on large tables, which is hugely important for streaming pipelines!
Comment · 5 months ago
A follow up to my previous post - icestream is an asynchronous compaction service for iceberg tables with many equality deletes (a symptom of frequent streaming writes on tables with "primary keys"). Now, instead of relying on Cassandra + Spark to index Apache Iceberg table data, Icestream uses Flink and Apache Paimon - enabling a separation between compute and storage and keeping an LSM tree style index on disk.
Comment · 6 months ago
Icestream is an asynchronous table maintenance tool for iceberg tables that converts equality deletes (write optimized) to positional deletes (read optimized). It does so efficiently by leveraging an index over the table data stored in Cassandra, and the cassandra-spark-connector, which enables efficient distributed nested-loop indexed joins from iceberg data in spark to the index data in the database.
Comment · 9 months ago
Hi! I forked this project from https://github.com/udaysagar2177/apache-iceberg-fileio in order to make it delegate between database and object store for data/metadata, as well as use reflection for use within other query engines outside of the java api.

While this isn't as good of a spec for database-metadata as something like ducklake would be, there are still many intrinsic benefits to avoiding object store for these many small writes.

See the repo: https://github.com/jordepic/icebase

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton