[
https://issues.apache.org/jira/browse/HIVE-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13223318#comment-13223318
]
Edward Capriolo commented on HIVE-2646:
---------------------------------------
Hive-2745 is really baked in. It is more then just built changes in the hive
code we build a bin/hadoop jar command and fork (this is really lame). The
non-standard tarball dependency is mostly caused by the fact that upstream
changes effect Hive. Hive does heavy work to maintain backwards compatibility
all the way to hadoop 0.20.2. Pig takes the other approach but you almost
always need to compile pig for your version of hadoop. You are right to say
that as long as upstream keeps changing we have to keep hacking. I will look at
the patch I am not sure what is the best way to handle supporting versions of
hadoop that are not even released yet.
> Hive Ivy dependencies on Hadoop should depend on jars directly, not tarballs
> ----------------------------------------------------------------------------
>
> Key: HIVE-2646
> URL: https://issues.apache.org/jira/browse/HIVE-2646
> Project: Hive
> Issue Type: Bug
> Components: Build Infrastructure
> Affects Versions: 0.8.0
> Reporter: Andrew Bayer
> Priority: Critical
> Attachments: HIVE-2646.diff.txt
>
>
> The current Hive Ivy dependency logic for its Hadoop dependencies is
> problematic - depending on the tarball and extracting the jars from there,
> rather than depending on the jars directly. It'd be great if this was fixed
> to actually have the jar dependencies defined directly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
