GitHub user vanzin opened a pull request:

    https://github.com/apache/spark/pull/19519

    [SPARK-21840][core] Add trait that allows conf to be directly set in 
application.

    Currently SparkSubmit uses system properties to propagate configuration to
    applications. This makes it hard to implement features such as SPARK-11035,
    which would allow multiple applications to be started in the same JVM. The
    current code would cause the config data from multiple apps to get mixed
    up.
    
    This change introduces a new trait, currently internal to Spark, that allows
    the app configuration to be passed directly to the application, without
    having to use system properties. The current "call main() method" behavior
    is maintained as an implementation of this new trait. This will be useful
    to allow multiple cluster mode apps to be submitted from the same JVM.
    
    As part of this, SparkSubmit was modified to collect all configuration
    directly into a SparkConf instance. Most of the changes are to tests so
    they use SparkConf instead of an opaque map.
    
    Tested with existing and added unit tests.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/vanzin/spark SPARK-21840

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/19519.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #19519
    
----
commit 8f31cf5ed7b22cb625e29c6dc0b8a01ff73cd8e1
Author: Marcelo Vanzin <[email protected]>
Date:   2017-10-17T17:21:50Z

    [SPARK-21840][core] Add trait that allows conf to be directly set in 
application.
    
    Currently SparkSubmit uses system properties to propagate configuration to
    applications. This makes it hard to implement features such as SPARK-11035,
    which would allow multiple applications to be started in the same JVM. The
    current code would cause the config data from multiple apps to get mixed
    up.
    
    This change introduces a new trait, currently internal to Spark, that allows
    the app configuration to be passed directly to the application, without
    having to use system properties. The current "call main() method" behavior
    is maintained as an implementation of this new trait. This will be useful
    to allow multiple cluster mode apps to be submitted from the same JVM.
    
    As part of this, SparkSubmit was modified to collect all configuration
    directly into a SparkConf instance. Most of the changes are to tests so
    they use SparkConf instead of an opaque map.
    
    Tested with existing and added unit tests.

----


---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to