hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-7349) Consuming published Hive HCatalog artificats in a Hadoop 2 build environment fails
Date Mon, 31 Aug 2015 12:35:45 GMT

    [ https://issues.apache.org/jira/browse/HIVE-7349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14723361#comment-14723361
] 

ASF GitHub Bot commented on HIVE-7349:
--------------------------------------

Github user jamescao commented on the pull request:

    https://github.com/apache/flink/pull/1079#issuecomment-136359875
  
    @chiwanpark 
    Yes, it's sure that the apache version of HCatalog is compiled against hadoop1. Using
this jar in an hadoop2 environment will lead to binary incompatibility error. I think Hive
community is aware of this problem.
    https://issues.apache.org/jira/browse/HIVE-7349
    On the other hand. The cloudera Hcatalog jar is compiled against hadoop2, thus works with
hadoop2 environment. But using cloudera jar in a hadoop1 environment will lead to binary incompatibility
error. I guess one way to solve this is to add a vendor-specific hcatalog-module for users
who want to use hcatalog in hadoop2 or we need to wait until hive community publish 2 artifacts
in maven for both hadoop1 and hadoop2. 


> Consuming published Hive HCatalog artificats in a Hadoop 2 build environment fails
> ----------------------------------------------------------------------------------
>
>                 Key: HIVE-7349
>                 URL: https://issues.apache.org/jira/browse/HIVE-7349
>             Project: Hive
>          Issue Type: Bug
>          Components: HCatalog
>    Affects Versions: 0.13.0
>            Reporter: Venkat Ranganathan
>
> The published Hive artifacts are built with Hadoop 1 profile.   Even though Hive has
Hadoop 1 and Hadoop 2 shims, some of the HCatalog Mapreduce classes are still dependent on
the compiled environment.
> For example, using Hive artifacts published in a Sqoop Hcatalog Hadoop 2 build environment
results in the following failure
> Found interface org.apache.hadoop.mapreduce.JobContext, but class was expected
> java.lang.IncompatibleClassChangeError: Found interface org.apache.hadoop.mapreduce.JobContext,
but class was expected
>         at org.apache.hive.hcatalog.mapreduce.HCatBaseOutputFormat.getJobInfo(HCatBaseOutputFormat.java:104)
>         at org.apache.hive.hcatalog.mapreduce.HCatBaseOutputFormat.getOutputFormat(HCatBaseOutputFormat.java:84)
>         at org.apache.hive.hcatalog.mapreduce.HCatBaseOutputFormat.checkOutputSpecs(HCatBaseOutputFormat.java:73)
>         at org.apache.hadoop.mapreduce.JobSubmitter.checkSpecs(JobSubmitter.java:418)
>         at org.apache.hadoop.mapreduce.JobSubmitter.submitJobInternal(JobSubmitter.java:333)
>         at org.apache.hadoop.mapreduce.Job$11.run(Job.java:1218)
>         at org.apache.hadoop.mapreduce.Job$11.run(Job.java:1215)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at javax.security.auth.Subject.doAs(Subject.java:396)
>         at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1478)
>         at org.apache.hadoop.mapreduce.Job.submit(Job.java:1215)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message