[
https://issues.apache.org/jira/browse/SPARK-6782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Armbrust resolved SPARK-6782.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.5.0
Issue resolved by pull request 5426
[https://github.com/apache/spark/pull/5426]
> add sbt-revolver plugin to sbt build
> ------------------------------------
>
> Key: SPARK-6782
> URL: https://issues.apache.org/jira/browse/SPARK-6782
> Project: Spark
> Issue Type: Improvement
> Components: Build
> Reporter: Imran Rashid
> Assignee: Imran Rashid
> Priority: Minor
> Fix For: 1.5.0
>
>
> [sbt-revolver|https://github.com/spray/sbt-revolver] is a very useful sbt
> plugin for development. You can start & stop long-running processes without
> being forced to kill the entire sbt session. This can save a lot of time in
> the development cycle.
> With sbt-revolver, you run {{re-start}} to start your app in a forked jvm.
> It immediately gives you the sbt shell back, so you can continue to code.
> When you want to reload your app with whatever changes you make, you just run
> {{re-start}} again -- it will kill the forked jvm, recompile your code, and
> start the process again. (Or you can run {{re-stop}} at any time to kill the
> forked jvm.)
> I used this a ton while working on adding json support to the UI in
> https://issues.apache.org/jira/browse/SPARK-3454 (as the history server never
> stops, without this plugin I had to kill sbt between every time I'd run it
> manually to play with the behavior.) I don't write a lot of spark-streaming
> jobs, but I've also used this plugin in that case, since again my streaming
> jobs never terminate -- I imagine it would be really useful to anybody that
> is modifying streaming and wants to test out running some jobs.
> I'll post a PR.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
