hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phabricator (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-2646) Hive Ivy dependencies on Hadoop should depend on jars directly, not tarballs
Date Thu, 08 Mar 2012 23:03:59 GMT

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

Phabricator commented on HIVE-2646:
-----------------------------------

thw has commented on the revision "HIVE-2646 [jira] Hive Ivy dependencies on Hadoop should
depend on jars directly, not tarballs".

INLINE COMMENTS
  shims/ivy.xml:34 My comment refers only to the hadoop dependencies below. You will never
have hadoop23 and hadoop20 configuration at the same time. Below is what we did in Pig, but
it gets really cluttered because now you have the stuff for 0.20 and 0.23, which is mutually
exclusive, in one file.


REVISION DETAIL
  https://reviews.facebook.net/D2133

BRANCH
  HIVE-2646-dev-branch

                
> 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.D2133.1.patch, HIVE-2646.D2133.2.patch, HIVE-2646.D2133.3.patch,
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

        

Mime
View raw message