[
https://issues.apache.org/jira/browse/DRILL-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15972948#comment-15972948
]
David Chaverri commented on DRILL-3036:
---------------------------------------
Is this going to be added anytime soon ? We are having issues with it, we need
to do a Select * in order to get the filter push down, but I think that's not
the idea. It would be great to have it working as expected.
> 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.15#6346)
