I don't. The hot-deploy shouldn't happen while there is a job running. At
least in the REPL it won't make much sense. It's a development-only
feature to shorten the iterative coding cycle. In production environment,
this is not enabled ... though there might be situations where it would be
desi
Thanks for the email. How do you deal with in-memory state that reference
the classes? This can happen in both streaming and caching in RDD and
temporary view creation in SQL.
On Mon, Jun 6, 2016 at 3:40 PM, S. Kai Chen wrote:
> Hi,
>
> We use spark-shell heavily for ad-hoc data analysis as well
Hi,
We use spark-shell heavily for ad-hoc data analysis as well as iterative
development of the analytics code. A common workflow consists the following
steps:
1. Write a small Scala module, assemble the fat jar
2. Start spark-shell with the assembly jar file
3. Try out some ideas in the
