Github user berngp commented on the pull request:
https://github.com/apache/spark/pull/116#issuecomment-38198767
@aarondav I am very glad you mentioned #86 . I am also working on it so
that the _Shell_ and _Submit_ script share a common setup and arguments,
presenting a unified view to _Spark Users_.
Now, let me see if I understand when you say "_probably be done using the
same pattern as that patch (and other "*Arguments" classes)_". My
interpretation is that we can provide a Scala, lets say Trait, that takes care
of Argument Parsing and can be shared across the Shell as well as the Submit
classes. If that is so, I agree and think its a great idea. I already started
work on that direction as a different feature/enhancement but something that
will be nice to flush out is how much **Bash vs Scala** we want to have for
argument parsing. I am not a fan of _Bash_ but as a user it is fast to execute
and get feedback, ergo you don't need to wait for a JVM to start. That said
from a development perspective I think its more efficient to use _Scala_ since
we can minimize the code for scripts that target specific operating systems,
mainly *NIX vs Windows.
CC> @sryza
PS. https://github.com/scopt/scopt might be a good option to provide
argument parsing in Scala or we could just build it using Sandy (@sryza) good
work.
---
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.
---
