GitHub user erenavsarogullari opened a pull request:
https://github.com/apache/spark/pull/16992
[SPARK-19662][SCHEDULER][TEST] Add Fair Scheduler Unit Test coverage for
different build cases
## What changes were proposed in this pull request?
Fair Scheduler can be built via one of the following options:
- By setting a `spark.scheduler.allocation.file` property,
- By setting `fairscheduler.xml` into classpath.
These options are checked **in order** and fair-scheduler is built via
first found option. If invalid path is found, `FileNotFoundException` will be
expected.
This PR aims unit test coverage of these use cases and a minor
documentation change has been added for second option(`fairscheduler.xml` into
classpath) to inform the user.
Also, This PR is related with #16813 and has been created seperatedly to
keep patch content as isolated and to help the reviewers.
## How was this patch tested?
Added new Unit Tests.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/erenavsarogullari/spark SPARK-19662
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/16992.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 #16992
----
commit 0b38e699538f8a890d9fd31cab14adf3e6e8c5c9
Author: erenavsarogullari <[email protected]>
Date: 2017-02-19T14:11:34Z
Add Fair Scheduler Unit Test coverage for different build cases
----
---
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]
