[
https://issues.apache.org/jira/browse/SPARK-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14070574#comment-14070574
]
Helena Edelson commented on SPARK-2593:
---------------------------------------
Yes, absolutely.
WRT tests, I haven't reviewed all of them but in many cases for ActorSystem
creation you want to pass in particular settings (Typesafe Config) per test or
group of tests, so this may make sense for some vs all. I will look into it.
That said, it would certainly be easy to write an abstract class that takes an
optional Config for testing with fallbacks to any defaults, in order to run one
ActorSystem and speed up the tests.
> Add ability to pass an existing Akka ActorSystem into Spark
> -----------------------------------------------------------
>
> Key: SPARK-2593
> URL: https://issues.apache.org/jira/browse/SPARK-2593
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Reporter: Helena Edelson
>
> As a developer I want to pass an existing ActorSystem into StreamingContext
> in load-time so that I do not have 2 actor systems running on a node in an
> Akka application.
> This would mean having spark's actor system on its own named-dispatchers as
> well as exposing the new private creation of its own actor system.
>
> I would like to create an Akka Extension that wraps around Spark/Spark
> Streaming and Cassandra. So the programmatic creation would simply be this
> for a user
> val extension = SparkCassandra(system)
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
