[
https://issues.apache.org/jira/browse/HIVE-984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834558#action_12834558
]
John Sichi commented on HIVE-984:
---------------------------------
Shims: you may be right, but I guess the principle is that all source code
checked in ought to be covered by the build if possible. It's arguable that we
should actually do even more in this respect (rather than less), since for
example in HIVE-1136 we just hit a case where one of my changes was
incompatible with an old Hadoop version (nothing to do with shims). If we
built against all supported Hadoop versions as part of ant test, this would
have been caught when I ran tests myself (so Zheng would never have had to
spend time testing my bad patch and rejecting it). ant test might be a
reasonable place for that, since test time will always be orders of magnitude
longer than build time. (But note: I'm not proposing to run tests on all
versions except in Hudson!)
Hudson automatically testing patches: I don't know the answer to that one, but
it sounds like a very high-value automation to me if the resources are
available, and my opinion on the version download issue might change if this
were working reliably with permanently committed resources.
archive.apache.org: the default mirroring for Hadoop seems to be 0.18.3,
0.19.2, and 0.20.1 (that's what I see when I browse most of the mirrors), which
doesn't match what Hive currently wants (0.17.2.1, 0.18.3, 0.19.0, and 0.20.0).
That's why I was thinking we might need a custom setup on mirror.facebook.net.
> 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.
