Hierarchical namespace support in Datafusion integration #1977
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.
Which issue does this PR close?
What changes are included in this PR?
In the PR, instead of just listing the top-level namespaces in the IcebergCatalogProvider, the namespaces are hierarchically traversed and made available using a dot notation ("parent.child").
Are these changes tested?
The first commit contains only a) unit test cases that safeguard existing functionality and b) a unit test to demonstrate the gap with hierarchical namespaces (i.e., fails before the fix). Besides the unit tests, there is an additional integration test cases that demonstrates that CRUD on tables in child namespaces works with Datafusion using the dot notation.