GitHub user YanTangZhai opened a pull request:

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

    [SPARK-2290] Worker should directly use its own sparkHome instead of 
appDesc.sparkHome when LaunchExecutor

    Worker should directly use its own sparkHome instead of appDesc.sparkHome 
when LaunchExecutor

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

    $ git pull https://github.com/YanTangZhai/spark SPARK-2290

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

    https://github.com/apache/spark/pull/1392.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 #1392
    
----
commit d3072fc05c7c20ec9d90732db2b9b26a4d27e290
Author: YanTangZhai <[email protected]>
Date:   2014-07-13T11:50:14Z

    Update ApplicationDescription.scala

commit 78ec6bc8c5d1af64ca21e1a231b47911df6d4f90
Author: YanTangZhai <[email protected]>
Date:   2014-07-13T11:52:34Z

    Update JsonProtocol.scala

commit 95e6ccc354167117430ce4cb7b2f5063a454ff1d
Author: YanTangZhai <[email protected]>
Date:   2014-07-13T11:54:55Z

    Update TestClient.scala

commit 508dcb65d04e3f12f99e03572a1cc277e7f1aeca
Author: YanTangZhai <[email protected]>
Date:   2014-07-13T11:58:01Z

    Update SparkDeploySchedulerBackend.scala

commit 6d6700aaad941779485eee2c35c4ab0cd278529e
Author: YanTangZhai <[email protected]>
Date:   2014-07-13T12:01:40Z

    Update Worker.scala

commit c360154ae5b03e7854d63573494fc6113295a7ec
Author: YanTangZhai <[email protected]>
Date:   2014-07-13T12:04:16Z

    Update JsonProtocolSuite.scala

commit 6febb215fb73735760fae957a4e71e2a61c17c77
Author: YanTangZhai <[email protected]>
Date:   2014-07-13T12:07:35Z

    Update ExecutorRunnerTest.scala

----


---
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