spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (SPARK-1126) spark-submit script for running compiled binaries
Date Sat, 29 Mar 2014 21:30:16 GMT


ASF GitHub Bot commented on SPARK-1126:

Github user pwendell commented on a diff in the pull request:
    --- Diff: docs/ ---
    @@ -50,6 +50,47 @@ The system currently supports three cluster managers:
     In addition, Spark's [EC2 launch scripts](ec2-scripts.html) make it easy to launch a
     cluster on Amazon EC2.
    +# Launching Applications
    --- End diff --
    Alright let's punt this to a broader doc clean-up for 1.0 which we can do during the QA
phase. I think that ideally yes, we should replace all of the mentions of the other clients
with this.

> spark-submit script for running compiled binaries
> -------------------------------------------------
>                 Key: SPARK-1126
>                 URL:
>             Project: Apache Spark
>          Issue Type: Bug
>          Components: Spark Core
>    Affects Versions: 0.9.0
>            Reporter: Sandy Pérez González
>            Assignee: Sandy Pérez González
>            Priority: Blocker
>             Fix For: 1.0.0
> It would be useful to have a script, roughly similar to the "hadoop jar" command that
is used for running compiled binaries against Spark.
> The script would do two things:
> * Set up the Spark classpath on the client side, so that users don't need to know where
Spark jars are installed or bundle all of Spark inside their app jar.
> * Provide a layer over the different modes that apps can be run, so that the same spark-jar
invocation could run the driver inside a YARN application master or in the client process,
depending on the cluster setup.

This message was sent by Atlassian JIRA

View raw message