[
https://issues.apache.org/jira/browse/HIVE-984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833665#action_12833665
]
Carl Steinbach commented on HIVE-984:
-------------------------------------
bq. Given HIVE-1120, I think the need to compile with only one version of
hadoop goes down a lot. What do you think?
That assumes that folks are able to satisfy the dependency at least once in
order to populate
their Ivy cache, and all of the traffic on hive-user seems to indicate this is
a lot harder than
it looks.
Right now we always build shims for four different minor versions of Hadoop:
0.17, 0.18, 0.19
and 0.20. Users also have the option of building against five different
versions of Hadoop
by setting hadoop.version to one that we don't already include. What's the long
term plan
here? Are we eventually going to build shims for ten different versions of
Hadoop every time
someone runs 'ant package'?
As I said earlier I think it makes sense to compile shims for as many different
versions as possible
when building a release tarball (or days from now when we want to build a Hive
POM),
but I don't see why we should force a user to do this now when list a specific
a Hadoop version
number using hadoop.version.
> Building Hive occasionally fails with Ivy error:
> hadoop#core;0.20.1!hadoop.tar.gz(source): invalid md5:
> -------------------------------------------------------------------------------------------------------
>
> Key: HIVE-984
> URL: https://issues.apache.org/jira/browse/HIVE-984
> Project: Hadoop Hive
> Issue Type: Bug
> Components: Build Infrastructure
> Reporter: Carl Steinbach
> Assignee: Carl Steinbach
> Attachments: HIVE-984.2.patch, HIVE-984.patch
>
>
> Folks keep running into this problem when building Hive from source:
> {noformat}
> [ivy:retrieve]
> [ivy:retrieve] :: problems summary ::
> [ivy:retrieve] :::: WARNINGS
> [ivy:retrieve] [FAILED ]
> hadoop#core;0.20.1!hadoop.tar.gz(source): invalid md5:
> expected=hadoop-0.20.1.tar.gz: computed=719e169b7760c168441b49f405855b72
> (138662ms)
> [ivy:retrieve] [FAILED ]
> hadoop#core;0.20.1!hadoop.tar.gz(source): invalid md5:
> expected=hadoop-0.20.1.tar.gz: computed=719e169b7760c168441b49f405855b72
> (138662ms)
> [ivy:retrieve] ==== hadoop-resolver: tried
> [ivy:retrieve]
> http://archive.apache.org/dist/hadoop/core/hadoop-0.20.1/hadoop-0.20.1.tar.gz
> [ivy:retrieve] ::::::::::::::::::::::::::::::::::::::::::::::
> [ivy:retrieve] :: FAILED DOWNLOADS ::
> [ivy:retrieve] :: ^ see resolution messages for details ^ ::
> [ivy:retrieve] ::::::::::::::::::::::::::::::::::::::::::::::
> [ivy:retrieve] :: hadoop#core;0.20.1!hadoop.tar.gz(source)
> [ivy:retrieve] ::::::::::::::::::::::::::::::::::::::::::::::
> [ivy:retrieve]
> [ivy:retrieve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
> {noformat}
> The problem appears to be either with a) the Hive build scripts, b) ivy, or
> c) archive.apache.org
> Besides fixing the actual bug, one other option worth considering is to add
> the Hadoop jars to the
> Hive source repository.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
