[jira] [Updated] (SPARK-5414) Add SparkListener implementation that allows users to receive all listener events in one method
[
https://issues.apache.org/jira/browse/SPARK-5414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Rosen updated SPARK-5414:
--
Target Version/s: 1.3.0 (was: 1.3.0, 1.2.1)
Add SparkListener implementation that allows users to receive all listener
events in one method
---
Key: SPARK-5414
URL: https://issues.apache.org/jira/browse/SPARK-5414
Project: Spark
Issue Type: New Feature
Components: Spark Core
Reporter: Josh Rosen
Assignee: Josh Rosen
Fix For: 1.3.0
Currently, users don't have a very good way to write a SparkListener that
receives all SparkListener events and which will be future-compatible (e.g.
it will receive events introduced in newer versions of Spark without having
to override new methods to process those events).
Therefore, I think Spark should include a concrete SparkListener
implementation that implements all of the message-handling methods and
dispatches all of them to a single {{onEvent}} method. By putting this code
in Spark, we isolate users from changes to the listener API.
--
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
[jira] [Updated] (SPARK-5414) Add SparkListener implementation that allows users to receive all listener events in one method
[
https://issues.apache.org/jira/browse/SPARK-5414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Rosen updated SPARK-5414:
--
Component/s: Spark Core
Add SparkListener implementation that allows users to receive all listener
events in one method
---
Key: SPARK-5414
URL: https://issues.apache.org/jira/browse/SPARK-5414
Project: Spark
Issue Type: New Feature
Components: Spark Core
Reporter: Josh Rosen
Assignee: Josh Rosen
Currently, users don't have a very good way to write a SparkListener that
receives all SparkListener events and which will be future-compatible (e.g.
it will receive events introduced in newer versions of Spark without having
to override new methods to process those events).
Therefore, I think Spark should include a concrete SparkListener
implementation that implements all of the message-handling methods and
dispatches all of them to a single {{onEvent}} method. By putting this code
in Spark, we isolate users from changes to the listener API.
--
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
