[#423] feat(core): Support the case-sensitive feature in gravitino catalog #1133
Conversation
This file contains 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.
What changes were proposed in this pull request?
Introduce interface
HasCatalogDefaultConfigto handle case-sensitive related problems in gravitino schemas and tables.Why are the changes needed?
The specific catalog has different behavior on case-sensitive issues with table and scheme names, entity stores in gravitino should take them into account and handle case-sensitive problems to maintain consistency with underlying catalog implementation like
Hive,Icebergand so on.Fix: #423
Does this PR introduce any user-facing change?
No
How was this patch tested?
New UT case named
testCaseSensitive