[
https://issues.apache.org/jira/browse/HIVE-7712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14095630#comment-14095630
]
Frank Kootte commented on HIVE-7712:
------------------------------------
I think that providing a proper build from the hive team would eleviate the
hive users from the hassle plus prevent people from chasing the same bug as I
did.
Is it possible for you to provide such a build ? Upstream would benefit from
this as well I presume.
> hive-exec-0.13.0.2.1.2.0-402.jar contains avro classes compiled against
> hadoop-v1
> ----------------------------------------------------------------------------------
>
> Key: HIVE-7712
> URL: https://issues.apache.org/jira/browse/HIVE-7712
> Project: Hive
> Issue Type: Bug
> Affects Versions: 0.13.0
> Reporter: Frank Kootte
> Assignee: Ashutosh Chauhan
> Priority: Critical
> Fix For: 0.14.0
>
>
> hive-exec-0.13.0.2.1.2.0-402.jar contains avro classes compiled against
> hadoop-v1.
> this causes issues on hadoop-v2 clusters where jobs are ran with this jar on
> the classpath.
> {code}
> Exception in thread "main" java.lang.IncompatibleClassChangeError: Found
> interface org.apache.hadoop.mapreduce.JobContext, but class was expected
> at
> org.apache.avro.mapreduce.AvroMultipleOutputs.getNamedOutputsList(AvroMultipleOutputs.java:208)
> at
> org.apache.avro.mapreduce.AvroMultipleOutputs.checkNamedOutputName(AvroMultipleOutputs.java:195)
> at
> org.apache.avro.mapreduce.AvroMultipleOutputs.addNamedOutput(AvroMultipleOutputs.java:259)
> at
> com.bol.searchrank.phase.calculate.CalculatePhaseRunner.createJob(CalculatePhaseRunner.java:70)
> {code}
> the issue is obfuscated due to the shaded nature of the jar which has no avro
> version references within itself anymore - which should probably be fixed as
> well to prevent such issue in the future and aid debugging properly.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
