-
Notifications
You must be signed in to change notification settings - Fork 29.3k
SPARK-1556. jets3t dep doesn't update properly with newer Hadoop versions #629
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
Changes from 3 commits
f21f356
bbed826
274f4f9
a2105fd
c3fa967
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -29,9 +29,21 @@ You can fix this by setting the `MAVEN_OPTS` variable as discussed before. | |
|
|
||
| ## Specifying the Hadoop version ## | ||
|
|
||
| Because HDFS is not protocol-compatible across versions, if you want to read from HDFS, you'll need to build Spark against the specific HDFS version in your environment. You can do this through the "hadoop.version" property. If unset, Spark will build against Hadoop 1.0.4 by default. | ||
|
|
||
| For Apache Hadoop versions 1.x, Cloudera CDH MRv1, and other Hadoop versions without YARN, use: | ||
| Because HDFS is not protocol-compatible across versions, if you want to read from HDFS, you'll need to build Spark against the specific HDFS version in your environment. You can do this through the "hadoop.version" property. If unset, Spark will build against Hadoop 1.0.4 by default. Note that certain build profiles are required for particular Hadoop versions: | ||
|
|
||
| <table class="table"> | ||
| <thead> | ||
| <tr><th>Hadoop version</th><th>Profile required</th></tr> | ||
| </thead> | ||
| <tbody> | ||
| <tr><td>0.23.x</td><td>hadoop-0.23</td></tr> | ||
| <tr><td>1.x to 2.1.x</td><td>(none)</td></tr> | ||
| <tr><td>2.2.x</td><td>hadoop-2.2</td></tr> | ||
| <tr><td>2.3.x and later</td><td>hadoop-2.3</td></tr> | ||
| </tbody> | ||
| </table> | ||
|
|
||
| For Apache Hadoop versions 1.x, Cloudera CDH "mr1" distributions, and other Hadoop versions without YARN, use: | ||
|
|
||
| # Apache Hadoop 1.2.1 | ||
| $ mvn -Dhadoop.version=1.2.1 -DskipTests clean package | ||
|
|
@@ -42,22 +54,40 @@ For Apache Hadoop versions 1.x, Cloudera CDH MRv1, and other Hadoop versions wit | |
| # Apache Hadoop 0.23.x | ||
| $ mvn -Phadoop-0.23 -Dhadoop.version=0.23.7 -DskipTests clean package | ||
|
|
||
| For Apache Hadoop 2.x, 0.23.x, Cloudera CDH MRv2, and other Hadoop versions with YARN, you can enable the "yarn-alpha" or "yarn" profile and set the "hadoop.version", "yarn.version" property. Note that Hadoop 0.23.X requires a special `-Phadoop-0.23` profile: | ||
| For Apache Hadoop 2.x, 0.23.x, Cloudera CDH, and other Hadoop versions with YARN, you can enable the "yarn-alpha" or "yarn" profile and optionally set the "yarn.version" property if it is different from "hadoop.version". The additional build profile required depends on the YARN version: | ||
|
|
||
| <table class="table"> | ||
| <thead> | ||
| <tr><th>YARN version</th><th>Profile required</th></tr> | ||
| </thead> | ||
| <tbody> | ||
| <tr><td>0.23.x to 2.1.x</td><td>yarn-alpha</td></tr> | ||
| <tr><td>2.2.x and later</td><td>yarn</td></tr> | ||
| </tbody> | ||
| </table> | ||
|
|
||
| Examples: | ||
|
|
||
| # Apache Hadoop 2.0.5-alpha | ||
| $ mvn -Pyarn-alpha -Dhadoop.version=2.0.5-alpha -DskipTests clean package | ||
|
|
||
| # Cloudera CDH 4.2.0 with MapReduce v2 | ||
| # Cloudera CDH 4.2.0 | ||
| $ mvn -Pyarn-alpha -Dhadoop.version=2.0.0-cdh4.2.0 -DskipTests clean package | ||
|
|
||
| # Apache Hadoop 2.2.X (e.g. 2.2.0 as below) and newer | ||
| $ mvn -Pyarn -Dhadoop.version=2.2.0 -DskipTests clean package | ||
|
|
||
| # Apache Hadoop 0.23.x | ||
| $ mvn -Pyarn-alpha -Phadoop-0.23 -Dhadoop.version=0.23.7 -Dyarn.version=0.23.7 -DskipTests clean package | ||
| $ mvn -Pyarn-alpha -Phadoop-0.23 -Dhadoop.version=0.23.7 -DskipTests clean package | ||
|
|
||
| # Apache Hadoop 2.2.X | ||
| $ mvn -Pyarn -Phadoop-2.2 -DskipTests clean package | ||
|
|
||
| # Apache Hadoop 2.3.X and newer | ||
| $ mvn -Pyarn -Phadoop-2.3 -DskipTests clean package | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Here also, I think it would be good to tell the user to set |
||
|
|
||
| # Apache Hadoop 2.4.X as a custom version | ||
| $ mvn -Pyarn -Phadoop-2.3 -Dhadoop.version=2.4.0 -DskipTests clean package | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should we just make a profile called
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. For instance, right now we suggest to use this for all hadoop-2.3+, but who knows if Hadoop will change it's dep graph in the future such that those builds don't actually work. It might be better to just create individual profiles for the ones we know we currently support via this workaround.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should be |
||
|
|
||
| # Different versions of HDFS and YARN. | ||
| $ mvn -Pyarn-alpha -Dhadoop.version=2.3.0 -Dyarn.version=0.23.7 -DskipTests clean package | ||
| $ mvn -Pyarn-alpha -Phadoop-2.3 -Dhadoop.version=2.3.0 -Dyarn.version=0.23.7 -DskipTests clean package | ||
|
|
||
| ## Spark Tests in Maven ## | ||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it might be better to always ask people to specify
hadoop.versionand then just explain that in some cases they need to add a profile to work around problems in the hadoop dependency graph. Otherwise sometimes we are relying on the profile to sethadoop.versionand it could be a bit confusing to users what is going on.I.e. for this example do:
The header here says "Apache Hadoop 2.2.X" but the actual example can't be directly generalized to 2.2.X (as it stands now) without them digging around the build more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why doesn't this work for Hadoop 2.2.0? I can fix the example. It should be matter of setting the version and profile, unless there is something deeper. In which case maybe the build needs to change in the hadoop-2.2 profile?