[
https://issues.apache.org/jira/browse/SPARK-20958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034310#comment-16034310
]
Cheng Lian commented on SPARK-20958:
------------------------------------
[~rdblue] I think the root cause here is we cherry-picked parquet-mr [PR
#318|https://github.com/apache/parquet-mr/pull/318] to parquet-mr 1.8.2, and
introduced this avro upgrade.
Tried to roll back parquet-mr back to 1.8.1 but it doesn't work well because
this brings back
[PARQUET-389|https://issues.apache.org/jira/browse/PARQUET-389] and breaks some
test cases involving schema evolution.
It would be nice if we can have a parquet-mr 1.8.3 or 1.8.2.1 release that has
[PR #318|https://github.com/apache/parquet-mr/pull/318] reverted from 1.8.2? I
think cherry-picking that PR is also problematic for parquet-mr because it
introduces a backward-incompatible dependency change in a maintenance release.
> Roll back parquet-mr 1.8.2 to parquet-1.8.1
> -------------------------------------------
>
> Key: SPARK-20958
> URL: https://issues.apache.org/jira/browse/SPARK-20958
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 2.2.0
> Reporter: Cheng Lian
> Assignee: Cheng Lian
>
> We recently realized that parquet-mr 1.8.2 used by Spark 2.2.0-rc2 depends on
> avro 1.8.1, which is incompatible with avro 1.7.6 used by parquet-mr 1.8.1
> and avro 1.7.7 used by spark-core 2.2.0-rc2.
> Basically, Spark 2.2.0-rc2 introduced two incompatible versions of avro
> (1.7.7 and 1.8.1). Upgrading avro 1.7.7 to 1.8.1 is not preferable due to the
> reasons mentioned in [PR
> #17163|https://github.com/apache/spark/pull/17163#issuecomment-286563131].
> Therefore, we don't really have many choices here and have to roll back
> parquet-mr 1.8.2 to 1.8.1 to resolve this dependency conflict.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
