[
https://issues.apache.org/jira/browse/SPARK-6324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Owen updated SPARK-6324:
-----------------------------
Assignee: Marcelo Vanzin
> Clean up usage code in command-line scripts
> -------------------------------------------
>
> Key: SPARK-6324
> URL: https://issues.apache.org/jira/browse/SPARK-6324
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Reporter: Marcelo Vanzin
> Assignee: Marcelo Vanzin
> Priority: Minor
> Fix For: 1.5.0
>
>
> With SPARK-4924, most of the logic to launch Spark classes is in a new Java
> library. Pretty much the only thing left in scripts are the usage strings for
> each command; that uses some rather ugly and hacky code to handle, since it
> requires the library communicating back with the scripts that they should
> print a usage string instead of executing a command.
> The scripts have to process that special command (differently on bash and
> Windows), and do filtering of the actual output of usage strings to account
> for different commands.
> Instead, the library itself should handle all this by executing the classes
> with a "help" argument; and the classes should be able to handle that
> argument to do the right thing. So this would require both changes in the
> launcher library, and in all the main entry points to make sure they properly
> respond to the "help" by printing the correct help message.
> This would make things a lot cleaner and a lot easier to maintain.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
