GitHub user vanzin opened a pull request:

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

    [SPARK-20191][yarn] Crate wrapper for RackResolver so tests can override it.

    Current test code tries to override the RackResolver used by setting
    configuration params, but because YARN libs statically initialize the
    resolver the first time it's used, that means that those configs don't
    really take effect during Spark tests.
    
    This change adds a wrapper class that easily allows tests to override the
    behavior of the resolver for the Spark code that uses it.

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

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

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

    https://github.com/apache/spark/pull/17508.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 #17508
    
----
commit 70e48fb7cce549ab0f5f06e7596e94b228cea824
Author: Marcelo Vanzin <[email protected]>
Date:   2017-04-02T00:22:07Z

    [SPARK-20191][yarn] Crate wrapper for RackResolver so tests can override it.
    
    Current test code tries to override the RackResolver used by setting
    configuration params, but because YARN libs statically initialize the
    resolver the first time it's used, that means that those configs don't
    really take effect during Spark tests.
    
    This change adds a wrapper class that easily allows tests to override the
    behavior of the resolver for the Spark code that uses 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.
---

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

Reply via email to