GitHub user zhengruifeng opened a pull request:

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

    [SPARK-15770][CORE][SQL][ML] Annotation audit for Experimental and 
DeveloperApi 2

    ## What changes were proposed in this pull request?
    1, remove comments `:: Experimental ::` for non-experimental API
    2, remove comments `:: DeveloperApi ::` for non-developer API
    2, add comments `:: Experimental ::` for experimental API
    3, add comments `:: DeveloperApi ::` for developerApi API
    4, reformat comments : `::DeveloperApi::` -> `:: DeveloperApi ::`, 
`::Experimental::` -> `:: Experimental ::`
    
    Use cmds like 
    `find . -name '*.scala' | xargs -i sh -c 'a=$(grep -c ":: Experimental ::" 
{}); b=$(grep -c "@Experimental" {}); echo {},$a,$b' | awk 'BEGIN{FS=","} 
$2!=$3{print $0}'` to verify coverage
    
    ## How was this patch tested?
    manual tests
    
    


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

    $ git pull https://github.com/zhengruifeng/spark annotation_check

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

    https://github.com/apache/spark/pull/13521.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 #13521
    
----
commit 7876272d113fd662e263890f5b8df917f8ab4b06
Author: Zheng RuiFeng <[email protected]>
Date:   2016-06-06T08:47:07Z

    create pr

commit c92235ba386b5e806beebc1ec68564bb16d4ff33
Author: Zheng RuiFeng <[email protected]>
Date:   2016-06-06T09:21:41Z

    check experimental

----


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to