[
https://issues.apache.org/jira/browse/SPARK-14358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496924#comment-15496924
]
Oleksiy Sayankin commented on SPARK-14358:
------------------------------------------
[~rxin], please see my comments here:
https://issues.apache.org/jira/browse/SPARK-17563, but I thinks yes, I can.
And after all I decided to create an issue
https://issues.apache.org/jira/browse/HIVE-14777
> Change SparkListener from a trait to an abstract class, and remove
> JavaSparkListener
> ------------------------------------------------------------------------------------
>
> Key: SPARK-14358
> URL: https://issues.apache.org/jira/browse/SPARK-14358
> Project: Spark
> Issue Type: Sub-task
> Components: Scheduler, Spark Core
> Reporter: Reynold Xin
> Assignee: Reynold Xin
> Fix For: 2.0.0
>
>
> Scala traits are difficult to maintain binary compatibility on, and as a
> result we had to introduce JavaSparkListener. In Spark 2.0 we can change
> SparkListener from a trait to an abstract class and then remove
> JavaSparkListener.
--
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
