[
https://issues.apache.org/jira/browse/SPARK-30784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yin Huai updated SPARK-30784:
-----------------------------
Description:
Originally reported at
[https://github.com/apache/spark/pull/26619#issuecomment-583802901]
Right now, Hive 2.3 profile pulls in regular orc, which depends on
hive-storage-api. However, hive-storage-api and hive-common have the following
common class files
org/apache/hadoop/hive/common/ValidReadTxnList.class
org/apache/hadoop/hive/common/ValidTxnList.class
org/apache/hadoop/hive/common/ValidTxnList$RangeResponse.class
For example,
[https://github.com/apache/hive/blob/rel/storage-release-2.6.0/storage-api/src/java/org/apache/hadoop/hive/common/ValidReadTxnList.java]
(pulled in by orc 1.5.8) and
[https://github.com/apache/hive/blob/rel/release-2.3.6/common/src/java/org/apache/hadoop/hive/common/ValidReadTxnList.java]
(from hive-common 2.3.6) both are in the classpath and they are different.
Having both versions in the classpath can cause unexpected behavior due to
classloading order. We should still use orc-nohive, which has hive-storage-api
shaded.
was:
Originally reported at
[https://github.com/apache/spark/pull/26619#issuecomment-583802901]
Right now, Hive 2.3 profile pulls in regular orc, which depends on
hive-storage-api. However, hive-storage-api and hive-common have the following
common class files
{{org/apache/hadoop/hive/common/ValidReadTxnList.class
org/apache/hadoop/hive/common/ValidTxnList.class
org/apache/hadoop/hive/common/ValidTxnList$RangeResponse.class}}
For example,
[https://github.com/apache/hive/blob/rel/storage-release-2.6.0/storage-api/src/java/org/apache/hadoop/hive/common/ValidReadTxnList.java]
(pulled in by orc 1.5.8) and
[https://github.com/apache/hive/blob/rel/release-2.3.6/common/src/java/org/apache/hadoop/hive/common/ValidReadTxnList.java]
(from hive-common 2.3.6) both are in the classpath and they are different.
Having both versions in the classpath can cause unexpected behavior due to
classloading order. We should still use orc-nohive, which has hive-storage-api
shaded.
> Hive 2.3 profile should still use orc-nohive
> --------------------------------------------
>
> Key: SPARK-30784
> URL: https://issues.apache.org/jira/browse/SPARK-30784
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 3.0.0
> Reporter: Yin Huai
> Priority: Blocker
>
> Originally reported at
> [https://github.com/apache/spark/pull/26619#issuecomment-583802901]
>
> Right now, Hive 2.3 profile pulls in regular orc, which depends on
> hive-storage-api. However, hive-storage-api and hive-common have the
> following common class files
>
> org/apache/hadoop/hive/common/ValidReadTxnList.class
> org/apache/hadoop/hive/common/ValidTxnList.class
> org/apache/hadoop/hive/common/ValidTxnList$RangeResponse.class
> For example,
> [https://github.com/apache/hive/blob/rel/storage-release-2.6.0/storage-api/src/java/org/apache/hadoop/hive/common/ValidReadTxnList.java]
> (pulled in by orc 1.5.8) and
> [https://github.com/apache/hive/blob/rel/release-2.3.6/common/src/java/org/apache/hadoop/hive/common/ValidReadTxnList.java]
> (from hive-common 2.3.6) both are in the classpath and they are different.
> Having both versions in the classpath can cause unexpected behavior due to
> classloading order. We should still use orc-nohive, which has
> hive-storage-api shaded.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
