spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Owen (JIRA)" <>
Subject [jira] [Updated] (SPARK-6324) Clean up usage code in command-line scripts
Date Fri, 05 Jun 2015 12:33:00 GMT


Sean Owen updated SPARK-6324:
    Assignee: Marcelo Vanzin

> Clean up usage code in command-line scripts
> -------------------------------------------
>                 Key: SPARK-6324
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message