-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-33298][CORE][FOLLOWUP] Add Unstable annotation to FileCommitProtocol
#33148
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
|
cc @HyukjinKwon and @cloud-fan please take a look when you have time, thanks. |
core/src/main/scala/org/apache/spark/internal/io/FileCommitProtocol.scala
Outdated
Show resolved
Hide resolved
FileCommitProtocolFileCommitProtocol
core/src/main/scala/org/apache/spark/internal/io/FileCommitProtocol.scala
Outdated
Show resolved
Hide resolved
|
Kubernetes integration test starting |
|
Kubernetes integration test status success |
|
Merged to master. |
|
Test build #140424 has finished for PR 33148 at commit
|
|
Thank you @HyukjinKwon and @dongjoon-hyun for review! |
What changes were proposed in this pull request?
This is the followup from #33012 (comment), where we want to add
@UnstabletoFileCommitProtocol, to give people a better idea of API.Why are the changes needed?
Make it easier for people to follow and understand code. Clean up code.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Existing unit tests, as no real logic change.