The reason for having two separate interfaces is developer API
backwards-compatibility, as far as I know. SparkFirehoseListener came later.
On Tue, Oct 13, 2015 at 4:36 PM, Jakob Odersky wrote:
> the path of the source file defining the event API is
> `core/src/main/scala/org/apache/spark/schedu
Check out SparkFirehoseListener, an adapter which forwards all events to a
single `onEvent` method in order to let you do pattern-matching as you have
described:
https://github.com/apache/spark/blob/master/core/src/main/java/org/apache/spark/SparkFirehoseListener.java
On Tue, Oct 13, 2015 at 4:29
the path of the source file defining the event API is
`core/src/main/scala/org/apache/spark/scheduler/SparkListener.scala`
On 13 October 2015 at 16:29, Jakob Odersky wrote:
> Hi,
> I came across the spark listener API while checking out possible UI
> extensions recently. I noticed that all event
Hi,
I came across the spark listener API while checking out possible UI
extensions recently. I noticed that all events inherit from a sealed trait
`SparkListenerEvent` and that a SparkListener has a corresponding
`onEventXXX(event)` method for every possible event.
Considering that events inherit
