Initial Iceberg sink implementation #46
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sauliusvl
force-pushed
the
iceberg_sink
branch
5 times, most recently
from
5f9a90d
to
d2b3203
Compare
|
@shivam247 could you please take a look? Once merged this should probably be released as |
sauliusvl
force-pushed
the
iceberg_sink
branch
8 times, most recently
from
d6d0aee
to
8676d01
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding a sink for Apache Iceberg tables.
The implementation achieves exactly-once delivery by committing files and storing offsets as table properties in a single Iceberg transaction. Because Iceberg only supports table level transactions we can only support sinking to individual tables, so e.g. it's not possible to branch out a single Kafka topic to multiple tables.
The integration test Iceberg loader uses a local Hadoop catalog, i.e. writes parquet files to local disk. To validate output we use DuckDB to query the table.