GitHub user felixcheung opened a pull request:

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

    [SPARK-15319][SPARKR][DOCS] Fix SparkR doc layout for corr and other 
DataFrame stats functions

    ## What changes were proposed in this pull request?
    
    Doc only changes. Please see screenshots.
    
    Before:
    http://spark.apache.org/docs/latest/api/R/statfunctions.html
    
![image](https://cloud.githubusercontent.com/assets/8969467/15264110/cd458826-1924-11e6-85bd-8ee2e2e1a85f.png)
    
    After
    
![image](https://cloud.githubusercontent.com/assets/8969467/15264126/f1260680-1924-11e6-93ad-24e0e5d30cce.png)
    (please ignore the style differences - this is due to not having the css in 
my local copy)
    
    This is still a bit weird. As discussed in SPARK-15237, I think the better 
approach is to separate out the DataFrame stats function instead of putting 
everything on one page. At least now it is clearer which description is on 
which function.
    
    
    ## How was this patch tested?
    
    Build doc


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

    $ git pull https://github.com/felixcheung/spark rstatdoc

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

    https://github.com/apache/spark/pull/13109.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 #13109
    
----
commit 756262cc9a095bd99a98a927361bc6a6bea5acf4
Author: felixcheung <[email protected]>
Date:   2016-05-13T23:03:00Z

    fix doc layout

----


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