[2.1][improvement](jdbc catalog) Optimize JdbcCatalog case mapping stability #43256
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
|
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
zy-kkk
force-pushed
the
jdbc_lower_21
branch
from
98d2e2a to
dbc92d6
Compare
zy-kkk
force-pushed
the
jdbc_lower_21
branch
from
dbc92d6 to
e44ca25
Compare
…ty (apache#41510) 1. Cancel the preservation of name mapping by IdentifierMapping, and only use it as the logic of case processing 2. Save the remote name in ExternalDatabase/ExternalTable object for get 3. Use fromRemoteXXName to process the remote name and map it to the local. Currently, only JdbcExternalCatalog uses IdentifierMapping for processing in this method, and other Catalogs are not processed. If processing is required, it should be extended by yourself 4. When lower_case_meta_name is true, the database, table, and column names mapped remotely to local will be checked to see if they are only case-sensitive. 5. Since Doris's column names are case-insensitive, column names will be checked at any time 6. When Fe config's lower_case_table_names is 1 or 2, the table names mapped from remote to local will be checked for only case-sensitive. 7. include/exclude_database_lists The remote name must be used 8. meta_names_mapping is used to resolve the conflicts mentioned above 9. If the same remoteName is in include_database_lists and meta_names_mapping, the filtered remoteName will be displayed according to the name mapped by meta_names_mapping 10. Since IdentifierMapping is no longer used to store the uppercase and lowercase name mapping, ExternalObject itself is used instead, which solves the problem of frequent refresh and small mapping loss 11. Remove the logic of rebuilding JdbcClient every time refreshCatalog
zy-kkk
force-pushed
the
jdbc_lower_21
branch
from
e44ca25 to
ba1abfa
Compare
|
run buildall |
|
run buildall |
|
run buildall |
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.
cherry-pick #41510