GitHub user Mironor opened a pull request:

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

    [SPARK-18708][CORE] Improvement/improve docs in spark context file

    ## What changes were proposed in this pull request?
    
    SparkContext.scala was created a long time ago and contains several types 
of Scaladocs/Javadocs mixed together. Public methods/fields should have a 
Scaladoc that is formatted in the same way everywhere. This pull request also 
adds scaladoc to methods/fields that did not have it before.
    
    ## How was this patch tested?
    
    No actual code was modified, only comments.
    
    Please review http://spark.apache.org/contributing.html before opening a 
pull request.


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

    $ git pull https://github.com/Mironor/spark 
improvement/improve-docs-in-spark-context-file

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

    https://github.com/apache/spark/pull/16137.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 #16137
    
----
commit 87bc74fb05a665b3972ce56e96df66dfd4c457fd
Author: Aliaksandr.Bedrytski <[email protected]>
Date:   2016-12-04T18:24:43Z

    Improves code style of the documentation in SparkContext.scala
    Adds documentation to public methods/fields that do not have it

commit 5d5236baab7c7889b9153fcd9c27b4839f075a8f
Author: Aliaksandr.Bedrytski <[email protected]>
Date:   2016-12-04T18:30:26Z

    Modifies line that exceeds 100 characters

----


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