[SPARK-45613][CORE] Expose DeterministicLevel as a DeveloperApi #43461
Conversation
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
added 3 commits
October 19, 2023 20:51
|
+CC @cloud-fan, @Ngone51, @dongjoon-hyun |
HyukjinKwon
approved these changes
Oct 20, 2023
HyukjinKwon
changed the title
cloud-fan
approved these changes
Oct 20, 2023
|
Merged to master. |
|
Thanks @HyukjinKwon, @cloud-fan ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
Expose
DeterministicLevelas aDeveloperApiWhy are the changes needed?
RDD.getOutputDeterministicLevelis aDeveloperApi- unfortunately, this cannot be overridden by users asDeterministicLevelisprivate[spark].Expose it as a
DeveloperApito allow users to override this.Does this PR introduce any user-facing change?
Yes, updates the visibility of
DeterministicLevelHow was this patch tested?
Visibility change, no test required.
Was this patch authored or co-authored using generative AI tooling?
No