[ 
https://issues.apache.org/jira/browse/SPARK-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sean Owen resolved SPARK-1306.
------------------------------
    Resolution: Fixed

I think this was obviated by subsequent changes to this documentation. SBT is 
no longer the focus, but, building-spark.md now has more comprehensive 
documentation on building with YARN, including these recent versions.

> no instructions provided for sbt assembly with Hadoop 2.2
> ---------------------------------------------------------
>
>                 Key: SPARK-1306
>                 URL: https://issues.apache.org/jira/browse/SPARK-1306
>             Project: Spark
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 0.9.0
>            Reporter: Diana Carroll
>
> on the running-on-yarn.html page, in the section "Building a YARN-Enabled 
> Assembly JAR", only the instructions for building for "old" Hadoop (2.0.5) 
> are provided.  There's a comment that "The build process now also supports 
> new YARN versions (2.2.x). See below."
> However, the only mention below is a single sentence which says "See Building 
> Spark with Maven for instructions on how to build Spark using the Maven 
> process."  There are no instructions for building with sbt. This is different 
> than in prior versions of the docs, in which a whole paragraph was provided.
> I'd like to see the command line to build for Hadoop 2.2 included right at 
> the top of the page. Also remove the bit about how it is "now" supported.   
> Hadoop 2.2 is now the "norm", no longer an exception, as I see it. 
> Unfortunately I'm not sure exactly what the command should be.  I tried this, 
> but got errors:
> SPARK_HADOOP_VERSION=2.2.0 SPARK_YARN=true sbt/sbt assembly



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

Reply via email to