[jira] [Updated] (DRILL-2019) Filter pushdown into the subquery when the subquery also has a filter is resulting in incorrect results

["Aman Sinha (JIRA)" <ji...@apache.org>]

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

Aman Sinha updated DRILL-2019:
------------------------------
    Attachment: 0001-DRILL-2019-Use-correct-index-for-filter-evaluation-w.patch

Uploaded patch.  Fix is to pass the correct index to doEval() in the filter template for SelectionVector2.  [~jnadeau] could you pls review ? 

> Filter pushdown into the subquery when the subquery also has a filter is resulting in incorrect results
> -------------------------------------------------------------------------------------------------------
>
>                 Key: DRILL-2019
>                 URL: https://issues.apache.org/jira/browse/DRILL-2019
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Execution - Operators, Query Planning & Optimization
>            Reporter: Rahul Challapalli
>            Assignee: Aman Sinha
>            Priority: Critical
>         Attachments: 0001-DRILL-2019-Use-correct-index-for-filter-evaluation-w.patch
>
>
> git.commit.id.abbrev=b491cdb
> The below query on top of tpch 0.01 data should actually return 0 records. (Verified with postgres). However drill returns incorrect result
> {code}
> select count(*) from cp.`tpch/lineitem.parquet` l inner join (select o.o_orderkey, o.o_custkey from cp.`tpch/orders.parquet` o where o.o_custkey < 5) s on l.l_orderkey = s.o_orderkey and s.o_custkey > 5;
> +------------+
> |   EXPR$0   |
> +------------+
> | 189        |
> +------------+
> {code}
> Marked as 'critical' since drill is reporting incorrect results



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