You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2017/11/20 20:09:01 UTC

[jira] [Updated] (SPARK-22564) csv reader no longer logs errors

     [ https://issues.apache.org/jira/browse/SPARK-22564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Owen updated SPARK-22564:
------------------------------
      Priority: Minor  (was: Major)
    Issue Type: Improvement  (was: Bug)

I don't see it used anywhere, though it still shows up in the pyspark API perhaps for backwards compatibility. It says it does nothing. I think this behavior change was therefore on purpose and this is at least not a bug, but I think you'd have to make the case this is important to revive. 

> csv reader no longer logs errors
> --------------------------------
>
>                 Key: SPARK-22564
>                 URL: https://issues.apache.org/jira/browse/SPARK-22564
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 2.2.0
>            Reporter: Adrian Bridgett
>            Priority: Minor
>
> Since upgrading from 2.0.2 to 2.2.0 we no longer see any malformed CSV warnings in the executor logs.  It looks like this maybe related to https://issues.apache.org/jira/browse/SPARK-19949 (where maxMalformedLogPerPartition was removed) as it seems to be used but AFAICT, not set anywhere.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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