GitHub user JoshRosen opened a pull request:

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

    [SPARK-17515] CollectLimit.execute() should perform per-partition limits

    ## What changes were proposed in this pull request?
    
    CollectLimit.execute() incorrectly omits per-partition limits, leading to 
performance regressions in case this case is hit (which should not happen in 
normal operation, but can occur in some cases (see #15068 for one example).
    
    ## How was this patch tested?
    
    Regression test in SQLQuerySuite that asserts the number of records scanned 
from the input RDD.

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

    $ git pull https://github.com/JoshRosen/spark SPARK-17515

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

    https://github.com/apache/spark/pull/15070.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 #15070
    
----
commit 506590753dbe59c71bf576751d3c2a50a70d9099
Author: Josh Rosen <joshro...@databricks.com>
Date:   2016-09-13T02:09:16Z

    Add regression test.

commit ac01f87f72e7df9c8c40a00822b98ebccb0ff1f6
Author: Josh Rosen <joshro...@databricks.com>
Date:   2016-09-13T02:09:24Z

    Fix by adding missing limit.

----


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to