[SPARK-39194][SQL] Add a pre resolution builder for spark session extensions#36563
Closed
yaooqinn wants to merge 2 commits intoapache:masterfrom
Closed
[SPARK-39194][SQL] Add a pre resolution builder for spark session extensions#36563yaooqinn wants to merge 2 commits intoapache:masterfrom
yaooqinn wants to merge 2 commits intoapache:masterfrom
Conversation
Member
Author
|
cc @cloud-fan @HyukjinKwon thanks |
|
We're closing this PR because it hasn't been updated in a while. This isn't a judgement on the merit of the PR in any way. It's just a way of keeping the PR queue manageable. |
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?
This PR aims to introduce an extension point for pre resolution.
Why are the changes needed?
A pre resolution enables developers or users to do some preparations before the actual resolution phase.
For example, the current catalog v2 implementations require setting SQL configurations ahead to activate, which is not flexible to use. Instead of using configuration, users are more likely to store and retrieve catalogs through meta storages, e.g. databases, kv stores, etc. The current relation resolution always falls back to the current/default catalog, which makes extra resolution rules unable to handle this issue. But W/ this feature we have opportunities to inject catalogs early.
Does this PR introduce any user-facing change?
it is a dev oriented change
How was this patch tested?
new tests