Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Tue, 7 Jul 2015 12:55:05 +0000 (UTC)
From: "Aman Sinha (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.12712384.1399316146000.116992.1436273705031@Atlassian.JIRA>
In-Reply-To: <JIRA.12712384.1399316146000@Atlassian.JIRA>
References: <JIRA.12712384.1399316146000@Atlassian.JIRA>
 <JIRA.12712384.1399316146591@arcas>
Subject: [jira] [Updated] (DRILL-636) Push Limit operator past project, left
 outer join, union all operator and down into scan operator
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Aman Sinha updated DRILL-636:
-----------------------------
    Fix Version/s:     (was: 1.2.0)
                   1.3.0

> Push Limit operator past project, left outer join, union all operator and down into scan operator 
> --------------------------------------------------------------------------------------------------
>
>                 Key: DRILL-636
>                 URL: https://issues.apache.org/jira/browse/DRILL-636
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components: Query Planning & Optimization
>            Reporter: Jinfeng Ni
>            Assignee: Aman Sinha
>             Fix For: 1.3.0
>
>
> When we have a limit operator on top of project, left outer join, union all operator, we should push the limit operator, until the limit is put into scan operator. Doing so, it will reduce the amount of data scanned by the scan operator.
> For instance,
> Select COL1, COL2 FROM T1 LIMIT 5;
> LIMIT (5)
>  \
> PROJECT (COL1, COL2)
>  \
> SCAN (T1).
> We need push limit past project, down into scan.
> Similar applies to left outer join, or union all.


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