[
https://issues.apache.org/jira/browse/DRILL-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Gilmore updated DRILL-3036:
--------------------------------
Attachment: DRILL-3036.1.patch.txt
I've modified the pushdown filter to match on both the filter/scan and
filter/project/scan operands and push the filter past the project in the latter
case accordingly.
> 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: B Anil Kumar
> 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)
