You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Wei Guo (Jira)" <ji...@apache.org> on 2023/02/03 10:56:00 UTC

[jira] [Created] (SPARK-42335) Add a legacy config for restoring writer's comment option behavior in CSV dataSource

Wei Guo created SPARK-42335:
-------------------------------

             Summary: Add a legacy config for restoring writer's comment option behavior in CSV dataSource
                 Key: SPARK-42335
                 URL: https://issues.apache.org/jira/browse/SPARK-42335
             Project: Spark
          Issue Type: Improvement
          Components: SQL
    Affects Versions: 3.3.0, 3.2.0, 3.1.0, 3.0.0
            Reporter: Wei Guo
             Fix For: 3.4.0


In PR [https://github.com/apache/spark/pull/29516], in order to fix some bugs, univocity-parsers used by CSV dataSource was upgraded from 2.8.3 to 2.9.0, it also involved a new feature of univocity-parsers that quoting values of the first column that start with the comment character. It made a breaking for users downstream that handing a whole row as input.
 
For codes:
{code:java}
Seq(("#abc", 1)).toDF.write.csv("/Users/guowei/comment_test") {code}
Before Spark 3.0,the content of output CSV files is shown as:
!image-2023-02-03-18-44-30-296.png!
After this change, the content is shown as:
!image-2023-02-03-18-15-12-661.png!
I have made a PR [https://github.com/uniVocity/univocity-parsers/pull/518] for issue [univocity-parsers#505|https://github.com/uniVocity/univocity-parsers/issues/505] to univocity-parses, but it seems to be a long time for waiting it to be merged.
 
For Spark, it's better to add a legacy config to restores the legacy behavior until univocity-parses releases a new version.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org