GitHub user vanzin opened a pull request:

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

    Fix two issues in ReplSuite.

    First, local cluster mode was failing because the backend impl was
    not passing correct arguments to start the executors (it was missing
    the number of cores).
    
    Second, when building the assembly with the maven "hadoop-provided"
    profile, the executors were failing to come up because Hadoop classes
    were not found in the classpath anymore; so add them explicitly to
    the classpath using spark.executor.extraClassPath. This is only
    needed for the local-cluster mode, but doesn't affect other tests,
    so it's added for all of them to keep the code simpler.

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

    $ git pull https://github.com/vanzin/spark repl-test-fix

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

    https://github.com/apache/spark/pull/781.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 #781
    
----
commit 30e454e76a5477212b1fdab656661f4c195f3237
Author: Marcelo Vanzin <[email protected]>
Date:   2014-05-14T23:09:52Z

    Fix two issues in ReplSuite.
    
    First, local cluster mode was failing because the backend impl was
    not passing correct arguments to start the executors (it was missing
    the number of cores).
    
    Second, when building the assembly with the maven "hadoop-provided"
    profile, the executors were failing to come up because Hadoop classes
    were not found in the classpath anymore; so add them explicitly to
    the classpath using spark.executor.extraClassPath. This is only
    needed for the local-cluster mode, but doesn't affect other tests,
    so it's added for all of them to keep the code simpler.

----


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