[
https://issues.apache.org/jira/browse/SPARK-14587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15239171#comment-15239171
]
Sean Owen commented on SPARK-14587:
-----------------------------------
That's a good change. It's worth reviewing all abstract class, and for that
matter traits, to see if any lack an explicit type. Browsing briefly I saw a
few more instances of this, like in MapOutputTracker.
> abstract class Receiver should be explicit about the return type of its
> methods
> -------------------------------------------------------------------------------
>
> Key: SPARK-14587
> URL: https://issues.apache.org/jira/browse/SPARK-14587
> Project: Spark
> Issue Type: Improvement
> Components: Streaming
> Affects Versions: 2.0.0
> Reporter: Jacek Laskowski
> Priority: Trivial
>
> The
> [org.apache.spark.streaming.receiver.Receiver|https://github.com/apache/spark/blob/master/streaming/src/main/scala/org/apache/spark/streaming/receiver/Receiver.scala#L102]
> abstract class defines API without specifying the return types explicitly,
> e.g.
> {code}
> def onStart()
> def onStop()
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
