Update on this:

We got the new mirror.facebook.net/facebook/hive-deps archive set up, and I've 
tested it out and changed the build.properties configuration to use it by 
default (Zheng has already committed this to trunk).  If you have been 
experiencing Hadoop download problems from archive.apache.org, please give it a 
try and let us know if you still have trouble.

For now, we only included the specific Hadoop versions pulled when no Hadoop 
version is specified.  Carl pointed out in HIVE-1192 that this will cause a 
failure if you specify another version like 0.20.1.

If you encounter this situation, override build.properties to point 
hadoop.mirror to a mirror location which contains the version you want.  The 
only one that contains every version is archive.apache.org, but you should NOT 
use this unless you really need it for an old Hadoop version.  Instead, if it's 
one of the two recent Hadoop versions below, you can find it in any mirror 
(e.g. http://mirror.facebook.net/apache, which is separate from the hive-deps 
archive):

0.19.2
0.20.1

I'll update the wiki to have this information too.

In a week or so, we'll be provisioning more resources to 
mirror.facebook.net/facebook/hive-deps so that we can serve any commonly needed 
Hadoop version from there.

JVS
________________________________________
From: John Sichi
Sent: Thursday, February 18, 2010 11:26 AM
To: hive-dev@hadoop.apache.org; hive-u...@hadoop.apache.org
Subject: ivy/hadoop downloads status update

Hi all,

We're working on the problem in HIVE-984 which a number of people have been 
hitting, and with luck we'll have a resolution within the next week or so.  To 
address it, we're setting up mirror.facebook.net<http://mirror.facebook.net> to 
serve the Hadoop versions needed by Hive, with better availability and 
reliability than archive.apache.org<http://archive.apache.org>.  Once we've got 
that deployed and tested out, I'll submit a patch to build.properties to point 
hadoop.mirror to the new location.

For now, if you need to get unblocked, use the workaround documented by Carl in 
the comments of that JIRA issue:

http://tinyurl.com/yajydoy

Thanks for your patience,
JVS

Reply via email to