You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Liang-Chi Hsieh (JIRA)" <ji...@apache.org> on 2016/11/19 02:15:58 UTC

[jira] [Closed] (SPARK-18089) Remove CollectLimitExec operator

     [ https://issues.apache.org/jira/browse/SPARK-18089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Liang-Chi Hsieh closed SPARK-18089.
-----------------------------------
    Resolution: Won't Fix

> Remove CollectLimitExec operator
> --------------------------------
>
>                 Key: SPARK-18089
>                 URL: https://issues.apache.org/jira/browse/SPARK-18089
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Liang-Chi Hsieh
>
> Currently, CollectLimitExec is an operator used when the logical Limit is the last operator in a logical plan. In fact, the job of CollectLimitExec is not different to GlobalLimitExec. We can do little refactoring to GlobalLimitExec and replace CollectLimitExec.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org