-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Refactor] add getCatalogDbName
and getCatalogTableName
in Table
(backport #53072)
#53150
Merged
+458
−490
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
Cherry-pick of 89be537 has failed:
To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally |
24 tasks
@mergify[bot]: Backport conflict, please reslove the conflict and resubmit the pr |
Signed-off-by: yanz <[email protected]>
dirtysalt
approved these changes
Nov 22, 2024
Quality Gate failedFailed conditions |
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.
Why I'm doing:
There are so many overlapped concepts and interfaces on tables
HiveMetaStoreTable
which basically have all interfaces inTable
getTableName
andgetName
to get table name.Table
should havegetDbName
as a basic method but actually does not have. And it leads many subclasses to havegetDbName
which is really bad.But there are some tricks right here: when you use resource mapping:
name
in table means the table name in local tablecatalogTableName
means the table name in catalogSo here is the solution:
getName
to get name in local tablegetCatalogTableName/getCatalogDBName
to get db/table in catalog.What I'm doing:
This PR is to:
getCatalogDbName()
in Table, which alsmost all subclasses need.getCatalogTableName()
HiveMetaStoreTable
concept from FE.Fixes #issue
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist:
Bugfix cherry-pick branch check:
This is an automatic backport of pull request #53072 done by [Mergify](https://mergify.com). ## Why I'm doing:
There are so many overlapped concepts and interfaces on tables
HiveMetaStoreTable
which basically have all interfaces inTable
getTableName
andgetName
to get table name.Table
should havegetDbName
as a basic method but actually does not have. And it leads many subclasses to havegetDbName
which is really bad.But there are some tricks right here: when you use resource mapping:
name
in table means the table name in local tablecatalogTableName
means the table name in catalogSo here is the solution:
getName
to get name in local tablegetCatalogTableName/getCatalogDBName
to get db/table in catalog.What I'm doing:
This PR is to:
getCatalogDbName()
in Table, which alsmost all subclasses need.getCatalogTableName()
HiveMetaStoreTable
concept from FE.Fixes #issue
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist: