Repository navigation
Document DataFusion integration refactor notes - #2
Draft
alexanderbianchi wants to merge 1 commit into
Draft
alexanderbianchi wants to merge 1 commit into
alexanderbianchi wants to merge 1 commit into
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
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.
Captures architectural notes and a proposed refactor sequence for the Iceberg DataFusion integration.
This is a draft for safekeeping and further iteration.
There are 3 actors to note
A SQL user generally should not deal with sessions or credentials. But the
caller constructing and registering IcebergCatalogProvider is not that SQL
user—it is the embedding application or framework.
That application already controls:
DataFusion is not Trino or Spark. It does not provide a standard
authenticated-session model, deployment architecture, coordinator/worker
boundary, or credential propagation protocol. Those are responsibilities of
systems built around it, such as df-executor, Spice, or Sail.
This makes a generic mapping like:
a questionable default. Iceberg cannot know:
The safer integration contract is:
A single-tenant application can still install an empty or service-level
context programmatically. A higher-level framework can provide convenience
wrappers. But the low-level integration should not weaken the trust
boundary to create an OOTB experience DataFusion itself does not promise.