[SPARK-27638][SQL][FOLLOW-UP] Format config name to follow the other boolean conf naming convention #27065
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
cloud-fan
approved these changes
Jan 2, 2020
HyukjinKwon
approved these changes
Jan 2, 2020
|
Test build #116004 has finished for PR 27065 at commit
|
|
Merged to master. |
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?
Change config name from
spark.sql.legacy.typeCoercion.datetimeToStringtospark.sql.legacy.typeCoercion.datetimeToString.enabled.Why are the changes needed?
To follow the other boolean conf naming convention.
Does this PR introduce any user-facing change?
No, it's newly added in Spark 3.0.
How was this patch tested?
Pass Jenkins