Add ability to call 'plugins' from the command-line

[tdanford]

Right now, each individual command-line ... command, that we run, is written as a separate AdamCommand and made a part of the adam-cli package.

That's great for common commands that are useful to everyone -- but in the future, users will want to write commands to execute on a Spark cluster with ADAM, without necessarily compiling the command into the adam-cli module itself.

This suggests that we might define an interface and an execution harness for "plugins," which would be dynamically-loaded code, conforming to a particular interface, that can be executed (by fully-qualified class name) from the command line.

[fnothaft]

+1

@heuermh had expressed interest in this as well.

[tdanford]

Pull request coming shortly, Frank :-)

[fnothaft]

Wunderbar!

[nealsid]

+1

On Thu, Feb 13, 2014 at 12:20 PM, Timothy Danford
notifications@git.luolix.topwrote:

Right now, each individual command-line ... command, that we run, is
written as a separate AdamCommand and made a part of the adam-cli package.

That's great for common commands that are useful to everyone -- but in the
future, users will want to write commands to execute on a Spark cluster
with ADAM, without necessarily compiling the command into the adam-cli
module itself.

This suggests that we might define an interface and an execution harness
for "plugins," which would be dynamically-loaded code, conforming to a
particular interface, that can be executed (by fully-qualified class name)
from the command line.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/101
.

[heuermh]

Sorry for coming late to the party here, looking at the current PluginExecutor I'm still missing a few things. How would an implementation of AdamPlugin add new command line parameters? How would an implementation of AdamPlugin not part of the adam build get added to the classpath?

[tdanford]

Yeah, we (Carl and I) talked about that -- especially the bit about specifying command-line arguments. We decided to file the pull request earlier rather than later, but these are great ideas and I agree that they're necessary. Want to file an issue or two? And then if you'd like to do some work, I'd be happy to review a PR ... or vice-versa, if I can find the time this weekend.

[heuermh]

Thanks, added new issues #130, #131, and #132.

I'm not very comfortable with scala yet, I'll see if I can work something out for 132 at least.