You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2016/04/15 14:18:25 UTC

[jira] [Resolved] (SPARK-14587) abstract class Receiver should be explicit about the return type of its methods

     [ https://issues.apache.org/jira/browse/SPARK-14587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Owen resolved SPARK-14587.
-------------------------------
    Resolution: Duplicate

Oh OK, I realize now that [~proflin] actually made a new JIRA for the more general change. That's fine but would have made some more sense to expand this one. No big deal but this one is now a duplicate

> 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: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org