Repository navigation
[core] Accept canonical REST identifier casing - #1110
Merged
JingsongLi merged 1 commit intoOct 12, 2026
Merged
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
2 participants
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.
Purpose
REST catalogs may return canonical database and table names whose ASCII casing differs from the requested identifier. Exact equality rejects those otherwise matching responses.
Accept case-only differences while retaining the response identifier so tables use the catalog canonical casing. Responses for a genuinely different database or table remain rejected.
Tests
cargo test -p paimon response_identifier_ --libcargo test -p paimon table::rest_env::tests --libcargo check -p paimon --all-targets --features fulltext,vortexcargo clippy -p paimon --all-targets --features fulltext,vortex -- -D warnings