Github user ScrapCodes commented on a diff in the pull request:
https://github.com/apache/spark/pull/10892#discussion_r51106802
--- Diff:
external/akka/src/main/scala/org/apache/spark/streaming/akka/ActorReceiver.scala
---
@@ -90,6 +90,48 @@ object ActorReceiver {
@DeveloperApi
abstract class ActorReceiver extends Actor {
+ /**
+ * start a new actor-based receiver, spark streaming will asynchronously
send the corresponding
+ * ActorRef object to the caller actor of this API
+ *
+ * @param props the props object of the receiver actor
+ * @param name the name of the actor
+ */
+ def startNewActorReceiver(props: Props, name: String) {
--- End diff --
The reason I did not create directly callable APIs for these is that result
is not received as a return value of the functions, instead it is received as a
message asynchronously. This is not the usual behavior of the API methods and
thus I was unsure about having them at all. @tdas thoughts ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
