[
https://issues.apache.org/jira/browse/SPARK-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14135835#comment-14135835
]
Patrick Wendell commented on SPARK-2593:
----------------------------------------
Hey [~helena] before you spend a lot of time on this - in Spark we haven't
exposed Akka as a public API and we have a policy in general of exposing third
party libraries in our API as little as possible. I could see us re-writing the
internal communication to not use Akka in the 1.X time frame, so I think there
could be resistance to anything that commits our API to akka.
We expect users who build apps on akka to maintain their own actor system. And
we are willing to trade off some minor inconveniences (e.g. tests are slower,
etc) for not having to support that API.
> 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.
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
