[WIP] Migrate Delta Lake tables to Iceberg #5097
Closed
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Work is in progress, but putting this out here for general feedback.
The idea will be to leverage the Delta Standalone library, rather than the DeltaCatalog, to read schema/partitioning/table metadata from the existing Delta Lake table. This simplifies the experience as users won't need to configure both a Delta Lake and Iceberg catalog as well as specify the mapping thereof.
A new action will be created to decouple the code behind this from the existing
migrateaction, which makes lots of assumptions about the incoming/exported catalog and relies on theSparkSessionCatalogto retrieve metadata about the state of the source table.