[SPARK-50759][SQL] Deprecate a few legacy Catalog APIs #50085
Closed
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
Contributor
|
I'm fine with it, cc @dongjoon-hyun |
Member
dongjoon-hyun
left a comment
dongjoon-hyun
left a comment
There was a problem hiding this comment.
Thank you for pinging me, @cloud-fan .
cc @huaxingao too.
Member
|
Also, cc @yaooqinn and @LuciferYang , too |
LuciferYang
dismissed
their stale review
The change is fine, but the Jira ID seems to be incorrect. Could you please double-check it?
Contributor
|
|
Contributor
|
These API looks not used anymore! +1 for this change. |
Contributor
|
thanks, merging to master! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
What changes were proposed in this pull request?
deprecate the following legacy APIs in Catalog
Why are the changes needed?
Deprecate the legacy APIs in favor of the new ones that accept qualified table names.
Does this PR introduce any user-facing change?
Yes
How was this patch tested?
existing tests
Was this patch authored or co-authored using generative AI tooling?
No