Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/12474#issuecomment-218470923
Yeah I would be a bit wary of just exposing ProcessBuilder without having a
way to do the startApplication. You don't want the user to have to do the
LaunchServer and ChildProc stuff. startApplication also sets
redirectErrorStream, which as mentioned above he seems to want to be able to
control also.
On the other hand I was just looking at better integration with oozie and
allowing passing processBuilder into startApplication would allow them to do
what they want. oozie doesn't want to have to rely on the spark-submit script
so if they could set any ProcessBuilder they could simply create one that does
SparkSubmit.main. But I would rather just see us add official support for that
use case.
I think it comes down to giving the user full control vs us having to
support funky use cases and them doing weird things.
---
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]
