You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2016/01/29 03:01:39 UTC
[jira] [Commented] (SPARK-13070) Points which physical file is the
trouble maker when Parquet schema merging fails
[ https://issues.apache.org/jira/browse/SPARK-13070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15122752#comment-15122752 ]
Apache Spark commented on SPARK-13070:
--------------------------------------
User 'liancheng' has created a pull request for this issue:
https://github.com/apache/spark/pull/10972
> Points which physical file is the trouble maker when Parquet schema merging fails
> ---------------------------------------------------------------------------------
>
> Key: SPARK-13070
> URL: https://issues.apache.org/jira/browse/SPARK-13070
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 2.0.0
> Reporter: Cheng Lian
> Assignee: Cheng Lian
> Priority: Minor
>
> As a user, I'd like to know which physical file is the trouble maker when Parquet schema merging fails. Currently, we only have an error message like this:
> {quote}
> Failed to merge incompatible data types LongType and IntegerType
> {quote}
> Would be nice to add the file path and the actual schema.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org