Skip to content

[SPARK-47307][DOCS][FOLLOWUP] Add a migration guide for the behavior change of base64 function #47371

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.

Sign up for GitHub

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

Closed
wForget wants to merge 2 commits into from
Closed

[SPARK-47307][DOCS][FOLLOWUP] Add a migration guide for the behavior change of base64 function #47371

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
777b7f7
[SPARK-47307][DOCS][FOLLOWUP] Add a migration guide for the behavior …
wForget Jul 16, 2024
c4bc0c0
address comment
wForget Jul 16, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/sql-migration-guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,6 +64,7 @@ license: |
## Upgrading from Spark SQL 3.5.1 to 3.5.2

- Since 3.5.2, MySQL JDBC datasource will read TINYINT UNSIGNED as ShortType, while in 3.5.1, it was wrongly read as ByteType.
- Since 3.5.2, the `base64` function will return a non-chunked string. To restore the previous behavior where base64 encoded strings that chunked into lines of at most 76 characters, set `spark.sql.legacy.chunkBase64String.enabled` to `true`.
Copy link
Member

@pan3793 pan3793 Jul 16, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the behavior changed in spark 3.3.0, so "the previous behavior" might be ambiguous.

Copy link
Member Author

@wForget wForget Jul 16, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense, I made a little change, thank you.


## Upgrading from Spark SQL 3.5.0 to 3.5.1

Expand Down