feat(datafusion) Add optional parameter to IcebergTableProvider so downstream Executors can re-register the Table#2876
Draft
NoahKusaba wants to merge 4 commits into
Conversation
NoahKusaba
marked this pull request as draft
July 22, 2026 03:16
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
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?
Related to feat(datafusion) Add snapshot_id parameter to pin table reads #2862
What changes are included in this PR?
Adds
IcebergCatalogConfig, a serializable, connection-free description of thecatalog and storage that backs a table, and threads it through the DataFusion
integration so it survives into the physical plan.
This allows optional serializable catalog/storage config, populated when this node is built through a config-backed provider, so it can be reconstructed on remote node by a distributed engine.
Are these changes tested?