[SPARK-47307][SQL][FOLLOWUP][3.5] Promote spark.sql.legacy.chunkBase64String.enabled from a legacy/internal config to a regular/public one #47416
Conversation
This file contains hidden or 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
…ng.enabled from a legacy/internal config to a regular/public one ### What changes were proposed in this pull request? + Promote spark.sql.legacy.chunkBase64String.enabled from a legacy/internal config to a regular/public one. + Add test cases for unbase64 ### Why are the changes needed? Keep the same behavior as before. More details: apache#47303 (comment) ### Does this PR introduce _any_ user-facing change? yes, revert behavior change introduced in apache#47303 ### How was this patch tested? existing unit test ### Was this patch authored or co-authored using generative AI tooling? No Closes apache#47410 from wForget/SPARK-47307_followup. Lead-authored-by: wforget <[email protected]> Co-authored-by: Kent Yao <[email protected]> Signed-off-by: Kent Yao <[email protected]> (cherry picked from commit af5eb08)
yaooqinn
approved these changes
Jul 19, 2024
LuciferYang
approved these changes
Jul 19, 2024
Member
|
cc @cloud-fan |
dongjoon-hyun
approved these changes
Jul 19, 2024
yaooqinn
pushed a commit
that referenced
this pull request
Jul 20, 2024
…4String.enabled from a legacy/internal config to a regular/public one Backports #47410 to 3.5 ### What changes were proposed in this pull request? + Promote spark.sql.legacy.chunkBase64String.enabled from a legacy/internal config to a regular/public one. + Add test cases for unbase64 ### Why are the changes needed? Keep the same behavior as before. More details: #47303 (comment) ### Does this PR introduce _any_ user-facing change? yes, revert behavior change introduced in #47303 ### How was this patch tested? existing unit test ### Was this patch authored or co-authored using generative AI tooling? No Closes #47416 from wForget/SPARK-47307_followup_3.5. Authored-by: wforget <[email protected]> Signed-off-by: Kent Yao <[email protected]>
Member
|
merged to branch-3.5. Thank you @wForget @LuciferYang @dongjoon-hyun |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Backports #47410 to 3.5
What changes were proposed in this pull request?
Why are the changes needed?
Keep the same behavior as before. More details: #47303 (comment)
Does this PR introduce any user-facing change?
yes, revert behavior change introduced in #47303
How was this patch tested?
existing unit test
Was this patch authored or co-authored using generative AI tooling?
No