Github user pwendell commented on a diff in the pull request:

    https://github.com/apache/spark/pull/896#discussion_r13108963
  
    --- Diff: docs/submitting-applications.md ---
    @@ -0,0 +1,153 @@
    +---
    +layout: global
    +title: Submitting Applications
    +---
    +
    +The `spark-submit` script in Spark's `bin` directory is used to launch 
applications on a cluster.
    +It can use all of Spark's supported [cluster 
managers](cluster-overview.html#cluster-manager-types)
    +through a uniform interface so you don't have to configure your 
application specially for each one.
    +
    +# Bundling Your Application's Dependencies
    +If your code depends on other projects, you will need to package them 
alongside
    +your application in order to distribute the code to a Spark cluster. To do 
this,
    +to create an assembly jar (or "uber" jar) containing your code and its 
dependencies. Both
    +[sbt](https://github.com/sbt/sbt-assembly) and
    +[Maven](http://maven.apache.org/plugins/maven-shade-plugin/)
    +have assembly plugins. When creating assembly jars, list Spark and Hadoop
    +as `provided` dependencies; these need not be bundled since they are 
provided by
    +the cluster manager at runtime. Once you have an assembled jar you can 
call the `bin/spark-submit`
    +script as shown here while passing your jar.
    +
    +For Python, you can use the `--py-files` argument of `spark-submit` to add 
`.py`, `.zip` or `.egg`
    +files to be distributed with your application. If you depend on multiple 
Python files we recommend
    +packaging them into a `.zip` or `.egg`.
    +
    +# Launching Applications with spark-submit
    +
    +Once a user application is bundled, it can be launched using the 
`bin/spark-submit` script
    --- End diff --
    
    This sentence needs a period. Wasn't part of your change but I just noticed 
it.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to