[
https://issues.apache.org/jira/browse/HIVE-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13225629#comment-13225629
]
Phabricator commented on HIVE-2646:
-----------------------------------
cwsteinbach 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 Aren't configurations the designated mechanism for handling
situations like this in Ivy? I don't see how breaking this into multiple files
will improve the situation. Won't that mean that we'll have to update multiple
files every time a new dependency is added instead of just one?
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
