GitHub user a-roberts opened a pull request:

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

    [SPARK-15821] [DOCS] Include parallel build info

    ## What changes were proposed in this pull request?
    
    (Please fill in changes proposed in this fix)
    Mention that users can build Spark using multiple threads to decrease build 
times
    
    ## How was this patch tested?
    
    (Please explain how this patch was tested. E.g. unit tests, integration 
tests, manual tests)
    Built on machines with between one core to 192 cores using mvn -T 1C and 
observed faster build times with no loss in stability
    
    In response to the question here 
https://issues.apache.org/jira/browse/SPARK-15821 I think we should suggest 
this option as we know it works for Spark and can result in faster builds

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

    $ git pull https://github.com/a-roberts/spark patch-3

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

    https://github.com/apache/spark/pull/13562.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 #13562
    
----
commit ce864e9b6721252900bdb5b2f90083e3c8bb65a0
Author: Adam Roberts <[email protected]>
Date:   2016-06-08T14:09:59Z

    [SPARK-15821] [DOCS] Include parallel build info
    
    In response to the question here 
https://issues.apache.org/jira/browse/SPARK-15821 I think we should suggest 
this option as we know it works for Spark and can result in faster builds

----


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