[SPARK-18662] Move resource managers to separate directory#16092
[SPARK-18662] Move resource managers to separate directory#16092foxish wants to merge 2 commits into
Conversation
|
/cc @tnachen |
|
There's a few other places that will need updating, including the spark/dev/sparktestsupport/modules.py Line 472 in 0a81121 spark/dev/sparktestsupport/modules.py Line 488 in 0a81121 |
|
Jenkins, this is ok to test |
|
Test build #69448 has finished for PR 16092 at commit
|
|
Hm, is this really necessary? I know it's just a move but for 2-3 modules, does it matter enough? |
|
Changed suggested by @rxin |
|
With a k8s backend on the way I do think it adds a nice organization for these 3 clearly grouped modules |
|
@JoshRosen Thanks for reviewing. |
|
Test build #69499 has finished for PR 16092 at commit
|
|
The test failure appears to be an unrelated flake. |
|
Test build #3465 has finished for PR 16092 at commit
|
|
@foxish this needs to be rebased. |
6763a80 to
3e78591
Compare
|
@vanzin Done. Thanks! |
|
Test build #69735 has finished for PR 16092 at commit
|
There was a problem hiding this comment.
You also need to update L477 (and probably a similar change in the mesos entry).
There was a problem hiding this comment.
@vanzin If I understand correctly, the sbt test goals can stay the same?
I can see them defined the same way for other modules such as sketch (as sketch/test), but it is nested under common/.
There was a problem hiding this comment.
Oh. Nevermind, I thought those were file paths like these. So fine the way they are.
There was a problem hiding this comment.
@vanzin also rebased after recent changes to HEAD. Is this okay to merge?
3e78591 to
05c478c
Compare
|
LGTM, merging to master. |
|
Thanks @vanzin :) |
|
Test build #69756 has finished for PR 16092 at commit
|
## What changes were proposed in this pull request? * Moves yarn and mesos scheduler backends to resource-managers/ sub-directory (in preparation for https://issues.apache.org/jira/browse/SPARK-18278) * Corresponding change in top-level pom.xml. Ref: apache#16061 (comment) ## How was this patch tested? * Manual tests /cc rxin Author: Anirudh <ramanathana@google.com> Closes apache#16092 from foxish/fix-scheduler-structure-2.
…n directory. ## What changes were proposed in this pull request? apache#16092 moves YARN resource manager related code to resource-managers/yarn directory. The test case ```YarnSchedulerBackendSuite``` was added after that but with the wrong place. I move it to correct directory in this PR. ## How was this patch tested? Existing test. Author: Yanbo Liang <ybliang8@gmail.com> Closes apache#16595 from yanboliang/yarn.
## What changes were proposed in this pull request? * Moves yarn and mesos scheduler backends to resource-managers/ sub-directory (in preparation for https://issues.apache.org/jira/browse/SPARK-18278) * Corresponding change in top-level pom.xml. Ref: apache#16061 (comment) ## How was this patch tested? * Manual tests /cc rxin Author: Anirudh <ramanathana@google.com> Closes apache#16092 from foxish/fix-scheduler-structure-2.
…n directory. ## What changes were proposed in this pull request? apache#16092 moves YARN resource manager related code to resource-managers/yarn directory. The test case ```YarnSchedulerBackendSuite``` was added after that but with the wrong place. I move it to correct directory in this PR. ## How was this patch tested? Existing test. Author: Yanbo Liang <ybliang8@gmail.com> Closes apache#16595 from yanboliang/yarn.
…n directory. ## What changes were proposed in this pull request? apache#16092 moves YARN resource manager related code to resource-managers/yarn directory. The test case ```YarnSchedulerBackendSuite``` was added after that but with the wrong place. I move it to correct directory in this PR. ## How was this patch tested? Existing test. Author: Yanbo Liang <ybliang8@gmail.com> Closes apache#16595 from yanboliang/yarn.
|
Will cc you on future issues. Apologies if this disrupted your workflow. It was meant to be a quick change only in code structure. |
What changes were proposed in this pull request?
Ref: #16061 (comment)
How was this patch tested?
/cc @rxin