[#5424] fix(paimon): remove duplicate schema names for Paimon catalog JDBC backend#5436
Merged
FANNG1 merged 1 commit intobranch-0.7from Nov 4, 2024
Conversation
… JDBC backend (#5434) ### What changes were proposed in this pull request? remove duplicate schema names after list schemas from Paimon ### Why are the changes needed? Fix: #5424 ### Does this PR introduce _any_ user-facing change? no ### How was this patch tested? test in local env, create schema s1, create table t1, will get only one schema not two schemas
FANNG1
approved these changes
Nov 4, 2024
jerryshao
deleted the
cherry-pick-branch-0.7-452d97ed2ee110506404dcb234d985cbb6d98a29
branch
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.
What changes were proposed in this pull request?
remove duplicate schema names after list schemas from Paimon
Why are the changes needed?
Fix: #5424
Does this PR introduce any user-facing change?
no
How was this patch tested?
test in local env, create schema s1, create table t1, will get only one schema not two schemas