Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Tue, 12 May 2015 07:30:00 +0000 (UTC)
From: "Adam Gilmore (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.12829103.1431414152000.83202.1431415800000@Atlassian.JIRA>
In-Reply-To: <JIRA.12829103.1431414152000@Atlassian.JIRA>
References: <JIRA.12829103.1431414152000@Atlassian.JIRA>
 <JIRA.12829103.1431414152071@arcas>
Subject: [jira] [Assigned] (DRILL-3036) Mongo plugin doesn't pushdown filter
 with a project
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Adam Gilmore reassigned DRILL-3036:
-----------------------------------

    Assignee: Adam Gilmore  (was: B Anil Kumar)

> Mongo plugin doesn't pushdown filter with a project
> ---------------------------------------------------
>
>                 Key: DRILL-3036
>                 URL: https://issues.apache.org/jira/browse/DRILL-3036
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Storage - MongoDB
>    Affects Versions: 0.9.0
>            Reporter: Adam Gilmore
>            Assignee: Adam Gilmore
>         Attachments: DRILL-3036.1.patch.txt
>
>
> Exacerbated by DRILL-2732, if a project exists between the scan and the filter, the current Mongo pushdown filter rule will not push the filter down into the scan.
> As implemented in DRILL-1950 and for the partition prune optimizer rule, the pushdown filter should handle the above scenario (by implementing the rule for both "filter/scan" and "filter/project/scan" scenarios).


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