You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Shuo Zheng (JIRA)" <ji...@apache.org> on 2016/04/18 19:15:25 UTC
[jira] [Updated] (SPARK-14702) Expose SparkLauncher's
ProcessBuilder for user flexibility
[ https://issues.apache.org/jira/browse/SPARK-14702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shuo Zheng updated SPARK-14702:
-------------------------------
Description:
SparkLauncher doesn't currently give too much flexibility in handling the Process that it spins up; for example I want to be able to direct output and error to files, set the working directory, etc. Currently the only two ways of interacting with the SparkLauncher is via {{launch()}} or {{startApplication(SparkAppHandle.Listener... listeners)}}.
I think we could give the user more power by making public {{createBuilder()}} (renamed to {{processBuilder()}} or {{getProcessBuilder()}}) to allow them to set the environment of the process however they want.
was:
SparkLauncher doesn't currently give too much flexibility in handling the Process that it spins up; for example I want to be able to direct output and error to files, set the working directory, etc. Currently the only two ways of interacting with the SparkLauncher is via `launch()` or `startApplication(SparkAppHandle.Listener... listeners)`.
I think we could give the user more power by making public `createBuilder()` (renamed to `processBuilder()` or `getProcessBuilder()`) to allow them to set the environment of the process however they want.
> Expose SparkLauncher's ProcessBuilder for user flexibility
> ----------------------------------------------------------
>
> Key: SPARK-14702
> URL: https://issues.apache.org/jira/browse/SPARK-14702
> Project: Spark
> Issue Type: Improvement
> Components: Spark Submit
> Affects Versions: 1.6.1
> Reporter: Shuo Zheng
> Original Estimate: 0.25h
> Remaining Estimate: 0.25h
>
> SparkLauncher doesn't currently give too much flexibility in handling the Process that it spins up; for example I want to be able to direct output and error to files, set the working directory, etc. Currently the only two ways of interacting with the SparkLauncher is via {{launch()}} or {{startApplication(SparkAppHandle.Listener... listeners)}}.
> I think we could give the user more power by making public {{createBuilder()}} (renamed to {{processBuilder()}} or {{getProcessBuilder()}}) to allow them to set the environment of the process however they want.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org