[
https://issues.apache.org/jira/browse/HIVE-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12862005#action_12862005
]
Carl Steinbach commented on HIVE-1192:
--------------------------------------
John/Bill: Ivy can't download the 0.20.1 tarball off of archive.apache.org
because
the associated md5 checksum file does not adhere to convention, i.e. it was not
created
by running 'md5sum' on the tarball.
For example, compare the following two files:
http://mirror.facebook.net/facebook/hive-deps/hadoop/core/hadoop-0.20.0/hadoop-0.20.0.tar.gz.md5
http://mirror.facebook.net/facebook/hive-deps/hadoop/core/hadoop-0.20.1/hadoop-0.20.1.tar.gz.md5
The checksum file for 0.20.0 contains the output of md5sum. The checksum file
for 0.20.1
contains a bunch of checksums generated using some other tool. Ivy barfs when
it tries to located
the md5 checksum in this mess.
> Build fails when hadoop.version=0.20.1
> --------------------------------------
>
> Key: HIVE-1192
> URL: https://issues.apache.org/jira/browse/HIVE-1192
> Project: Hadoop Hive
> Issue Type: Bug
> Components: Build Infrastructure
> Reporter: Carl Steinbach
>
> Setting hadoop.version=0.20.1 causes the build to fail since
> mirror.facebook.net/facebook/hive-deps does not have 0.20.1
> (only 0.17.2.1, 0.18.3, 0.19.0, 0.20.0).
> Suggested fix:
> * remove/ignore the hadoop.version configuration parameter
> or
> * Remove the patch numbers from these archives and use only the major.minor
> numbers specified by the user to locate the appropriate tarball to download,
> so 0.20.0 and 0.20.1 would both map to hadoop-0.20.tar.gz.
> * Optionally create new tarballs that only contain the components that are
> actually needed for the build (Hadoop jars), and remove things that aren't
> needed (all of the source files).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
