You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Takuya Ueshin (JIRA)" <ji...@apache.org> on 2014/10/03 04:10:33 UTC

[jira] [Updated] (SPARK-3771) AppendingParquetOutputFormat should use reflection to prevent from breaking binary-compatibility.

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

Takuya Ueshin updated SPARK-3771:
---------------------------------
    Summary: AppendingParquetOutputFormat should use reflection to prevent from breaking binary-compatibility.  (was: AppendingParquetOutputFormat should use reflection to prevent breaking binary-compatibility.)

> AppendingParquetOutputFormat should use reflection to prevent from breaking binary-compatibility.
> -------------------------------------------------------------------------------------------------
>
>                 Key: SPARK-3771
>                 URL: https://issues.apache.org/jira/browse/SPARK-3771
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 1.1.0
>            Reporter: Takuya Ueshin
>
> Original problem is [SPARK-3764|https://issues.apache.org/jira/browse/SPARK-3764].
> {{AppendingParquetOutputFormat}} uses a binary-incompatible method {{context.getTaskAttemptID}}.
> This causes binary-incompatible of Spark itself, i.e. if Spark itself is built against hadoop-1, the artifact is for only hadoop-1, and vice versa.



--
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