-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-48121][K8S] Promote KubernetesDriverConf to DeveloperApi
#46373
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
Conversation
dongjoon-hyun
left a comment
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.
Please file a JIRA issue, @jiangzho .
|
One more thing. If you have some time, please review the following PR on |
KubernetesDriverConf to DeveloperApiKubernetesDriverConf to DeveloperApi
KubernetesDriverConf to DeveloperApiKubernetesDriverConf to DeveloperApi
| } | ||
|
|
||
| private[spark] class KubernetesDriverConf( | ||
|
|
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.
Please remove this redundant empty line addition.
| */ | ||
| @Unstable | ||
| @DeveloperApi | ||
| @Since("4.0.0") |
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.
Ya, I hope we can make it stable from 4.0.0.
dongjoon-hyun
left a comment
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.
+1, LGTM.
|
Merged to master for Apache Spark 4.0.0-preview. |
What changes were proposed in this pull request?
This PR aims to promote
KubernetesDriverConftoDeveloperApiWhy are the changes needed?
Since Apache Spark Kubernetes Operator requires this, we had better maintain it as a developer API officially from Apache Spark 4.0.0.
apache/spark-kubernetes-operator#10
Does this PR introduce any user-facing change?
No
How was this patch tested?
Pass the CIs
Was this patch authored or co-authored using generative AI tooling?
No