Skip to content

Conversation

@c21
Copy link
Contributor

@c21 c21 commented Jun 30, 2021

What changes were proposed in this pull request?

This is the followup from #33012 (comment), where we want to add @Unstable to FileCommitProtocol, 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.

@github-actions github-actions bot added the CORE label Jun 30, 2021
@c21
Copy link
Contributor Author

c21 commented Jun 30, 2021

cc @HyukjinKwon and @cloud-fan please take a look when you have time, thanks.

@c21 c21 changed the title [SPARK-33298][CORE][FOLLOWUP] Add Unstable annotation to newly added methods of FileCommitProtocol [SPARK-33298][CORE][FOLLOWUP] Add Unstable annotation to FileCommitProtocol Jun 30, 2021
@SparkQA
Copy link

SparkQA commented Jun 30, 2021

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44939/

@SparkQA
Copy link

SparkQA commented Jun 30, 2021

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44939/

@HyukjinKwon
Copy link
Member

Merged to master.

@SparkQA
Copy link

SparkQA commented Jun 30, 2021

Test build #140424 has finished for PR 33148 at commit d41ba14.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@c21
Copy link
Contributor Author

c21 commented Jun 30, 2021

Thank you @HyukjinKwon and @dongjoon-hyun for review!

@c21 c21 deleted the bucket-followup branch June 30, 2021 08:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants