feat(datafusion): Serializable Codec for Distributed Engines#2727
Draft
NoahKusaba wants to merge 1 commit into
Draft
feat(datafusion): Serializable Codec for Distributed Engines#2727NoahKusaba wants to merge 1 commit into
NoahKusaba wants to merge 1 commit into
Conversation
NoahKusaba
changed the title
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.
Which issue does this PR close?
Add Enhancements to datafusion-iceberg crate, for future ballista-iceberg integration (which will be put another repo)
#2613
Iceberg's DataFusion physical plan nodes hold live, non-serializable handles — an Arc, a Table with an open FileIO, a PartitionValueCalculator. A distributed engine (Ballista) has to serialize plans and ship them to remote executors, which it can't do with those handles. This branch adds the minimal serializable seed needed to reconstruct those handles on a remote node, plus the public API surface for an external codec to read that seed out of a node and rebuild it. Everything is additive and opt-in: the config is always Option, defaulting to None, which preserves existing single-node behavior unchanged.
Are these changes tested?
Yes