hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brock Noland (JIRA)" <>
Subject [jira] [Commented] (HIVE-4305) Use a single system for dependency resolution
Date Mon, 08 Apr 2013 14:43:16 GMT


Brock Noland commented on HIVE-4305:

Hi Carl,

Absolutely. I don't want to push the hive community towards a tool they don't like, however
the community seems to be sitting on the fence.

1. Since many users/developers work on other projects in the ecosystem, there is no learning
curve for hive. For example, I use maven on Hadoop, Crunch, MRUnit, and Flume among others.
I have never used ivy and therefore I have learn two tools to do the same thing. Given the
widespread use of maven in the Hadoop ecosystem, it's fair to say I am not the only person
who has had to learn ivy for Hive.

2. Since dependency resolution will be done by other projects on my machine, using maven shares
that cache. This is a non-trivial amount of build time.

3. Maven has an "offline" mode which can be enabled on the command line. Ivy allows you to
set ttl to "eternal" but this does not disable downloads entirely. I believe there is an offline
mode, but as I understand it requires modification of the build configuration. Since I am
no ivy expert, see #1, I got this information from this page:

The big benefit from my perspective is #1. Cross pollination among projects is easier if learning
a new dependency resolution tool is not required. Therefore, if all else is equal, maven is
a good choice.
> Use a single system for dependency resolution
> ---------------------------------------------
>                 Key: HIVE-4305
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: Build Infrastructure, HCatalog
>            Reporter: Travis Crawford
> Both Hive and HCatalog use ant as their build tool. However, Hive uses ivy for dependency
resolution while HCatalog uses maven-ant-tasks. With the project merge we should converge
on a single tool for dependency resolution.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message