GitHub user vanzin opened a pull request:

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

    [SPARK-20421][core] Mark internal listeners as deprecated.

    These listeners weren't really meant for external consumption, but they're
    public and marked with @DeveloperApi. Adding the deprecated tag warns people
    that they may soon go away (as they will as part of the work for 
SPARK-18085.
    
    Note that not all types made public by 
https://github.com/apache/spark/pull/648
    are being deprecated. Some remaining types are still exposed through the
    SparkListener API.
    
    Also note the text for StorageStatus is a tiny bit different, since I'm not
    so sure I'll be able to remove it. But the effect for the users should be 
the
    same (they should stop trying to use it).


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

    $ git pull https://github.com/vanzin/spark SPARK-20421

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

    https://github.com/apache/spark/pull/17766.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 #17766
    
----
commit d16be2b004c7b2f7ca34faf8bdd993cf0445694b
Author: Marcelo Vanzin <van...@cloudera.com>
Date:   2017-04-25T23:16:20Z

    [SPARK-20421][core] Mark internal listeners as deprecated.
    
    These listeners weren't really meant for external consumption, but they're
    public and marked with @DeveloperApi. Adding the deprecated tag warns people
    that they may soon go away (as they will as part of the work for 
SPARK-18085.
    
    Note that not all types made public by 
https://github.com/apache/spark/pull/648
    are being deprecated. Some remaining types are still exposed through the
    SparkListener API.
    
    Also note the text for StorageStatus is a tiny bit different, since I'm not
    so sure I'll be able to remove it. But the effect for the users should be 
the
    same (they should stop trying to use it).

----


---
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