GitHub user vectorijk opened a pull request:

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

    [SPARK-15672][R][DOC] R programming guide update

    ## What changes were proposed in this pull request?
    Guide for
    - UDFs with dapply, dapplyCollect
    - spark.lapply for running parallel R functions
    
    ## How was this patch tested?
    build locally
    <img width="654" alt="screen shot 2016-06-14 at 03 12 56" 
src="https://cloud.githubusercontent.com/assets/3419881/16039344/12a3b6a0-31de-11e6-8d77-fe23308075c0.png";>


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

    $ git pull https://github.com/vectorijk/spark spark-15672-R-guide-update

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

    https://github.com/apache/spark/pull/13660.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 #13660
    
----
commit adee4d46551c379cb3c092d603041551f779c630
Author: Kai Jiang <[email protected]>
Date:   2016-06-06T04:41:42Z

    revise documentation for sparkr

commit 9081a0bf5072da5f5255f7ffcf398758ff19b46c
Author: Kai Jiang <[email protected]>
Date:   2016-06-06T04:41:42Z

    revise documentation for sparkr

commit 1ba263498c68ec41ec0096cdb305205a8f99f058
Author: Kai Jiang <[email protected]>
Date:   2016-06-14T09:31:08Z

    Merge branch 'spark-15672-R-guide-update' of github.com:vectorijk/spark 
into spark-15672-R-guide-update

commit 2611549e60f68d6ba12ec10b471dc96944508873
Author: Kai Jiang <[email protected]>
Date:   2016-06-14T10:08:25Z

    update

----


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