-
Notifications
You must be signed in to change notification settings - Fork 28.5k
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
[SPARK-51073][SQL] Remove Unstable
from SparkSessionExtensionsProvider
trait
#49780
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh actually, I would prefer to have this as unstable because it can touch stuff like optimizer and analyzer rules that are internal API..
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I understand we won't likely remove
SparkSessionExtensions
, and this is service loader forSparkSessionExtensions
(as mentioned in PR description). But I would prefer to avoid promoting this.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you elaborate a little more about how
SparkSessionExtensionsProvider
are affected with a change ofSparkSessionExtensions
? IIUC, we are not going to remove or rename classSparkSessionExtensions
.ServiceLoader
is only related to the relation between the text resource file and class name,SparkSessionExtensions
, isn't it?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe, are you considering removing this
ServiceLoader
pattern, @HyukjinKwon ?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mean, nothing will be affected by this ... I just worry that more people may
SparkSessionExtensions
itself...TBH, I personally don't like this
SparkSessionExtensions
in general because it opens too much catalyst API usage, and touching rules.. and I was thinking about having them all asUnstable
for now..I actually don't like all those API ... such as
df.queryExecution
, etc. for the same reason.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am fine if others are okay - I don't have a strong opinion.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I understand your concerns fully. I also understand why this is in this status. However, Apache Spark depends on this since v2.2.0 (SPARK-18127) because this is the only way for certain features.
The goal of this PR is only this
ServiceLoader
pattern is applicable in the stable contract for the production usage (SRE or dev team) in Spark 4.1.0.If many people are reluctant, I'm also going to drop this~ So, let's see.