-
Notifications
You must be signed in to change notification settings - Fork 587
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use $HADOOP_PREFIX if available #844
Comments
As always, there's a wrinkle. When using |
Good grief, a lot of installs seem to keep the |
Fortunately, the only ways we use these options are:
We could easily look for the hadoop binary in both Also, EMR now supports Hadoop 2.2.0, so I can poke around on there. |
Well, EMR's Hadoop 2.2.0 uses Actually, it looks like |
Yeah, looks like we should support |
Here's a simlar ticket from another library that uses Hadoop. |
If we want to use the new |
And the log dir can be pretty much anywhere, including |
Moving this issue out of 0.4.3 release since it seems a bit complicated. Will re-evaluate it once the current release is done. |
The 3.6.0 AMI uses The log directory is |
Note that we don't currently have a test that the |
Replaced by #1160. |
$HADOOP_HOME
is actually a bit deprecated; newer versions of Hadoop use$HADOOP_PREFIX
instead.If neither the
hadoop_home
option nor$HADOOP_HOME
is set, mrjob should use$HADOOP_PREFIX
.The text was updated successfully, but these errors were encountered: