GitHub user ksakellis opened a pull request:

    https://github.com/apache/spark/pull/3711

    [SPARK-4857] [CORE] Adds Executor membership events to SparkListener

    Adds onExecutorAdded and onExecutorRemoved events to the SparkListener. 
This will allow a client to get notified when an executor has been 
added/removed and provide additional information such as how many vcores it is 
consuming.
    
    In addition, this commit adds a SparkListenerAdapter to the Java API that 
provides default implementations to the SparkListener. This is to get around 
the fact that default implementations for traits don't work in Java. Having 
Java clients extend SparkListenerAdapter moving forward will prevent breakage 
in java when we add new events to SparkListener.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ksakellis/spark kostas-spark-4857

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/3711.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3711
    
----
commit b1f715d2c4c169bbc33175ea7984af22a7b941f8
Author: Kostas Sakellis <kos...@cloudera.com>
Date:   2014-12-16T08:55:01Z

    [SPARK-4857] [CORE] Adds Executor membership events to SparkListener
    
    Adds onExecutorAdded and onExecutorRemoved events to the
    SparkListener. This will allow a client to get notified when an
    executor has been added/removed and provide additional information
    such as how many vcores it is consuming.
    
    In addition, this commit adds a SparkListenerAdapter to the
    Java API that provides default implementations to the SparkListener.
    This is to get around the fact that default implementations for
    traits don't work in Java. Having Java clients extend
    SparkListenerAdapter moving forward will prevent breakage in java
    when we add new events to SparkListener.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to