anchovYu opened a new pull request, #36110:
URL: https://github.com/apache/spark/pull/36110

   ### What changes were proposed in this pull request?
   <!--
   Please clarify what changes you are proposing. The purpose of this section 
is to outline the changes and how this PR fixes the issue. 
   If possible, please consider writing useful notes for better and faster 
reviews in your PR. See the examples below.
     1. If you refactor some codes with changing classes, showing the class 
hierarchy will help reviewers.
     2. If you fix some SQL features, you can provide some references of other 
DBMSes.
     3. If there is design documentation, please add the link.
     4. If there is a discussion in the mailing list, please add the link.
   -->
   Add a legacy flag 
`spark.sql.legacy.nullValueWrittenAsUnquotedEmptyStringCsv.enabled` for the 
breaking changed introduced in https://github.com/apache/spark/pull/34853 and 
https://github.com/apache/spark/pull/34905 (followup).
   
   The flag is enabled by default, so the null values written as csv will 
output an unquoted empty string. When the flag is disabled, the null will 
output quoted empty string.
   
   ### Why are the changes needed?
   The original commit is a breaking change, and breaking changes should be 
encouraged to add a flag to turn it off for smooth migration between versions.
   
   ### Does this PR introduce _any_ user-facing change?
   With the default value of the conf, there is no user-facing difference.
   If users turn this conf off, they can restore the pre-change behavior.
   
   ### How was this patch tested?
   Through unit tests.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to