Rahul Challapalli created DRILL-2044:
----------------------------------------

             Summary: Filter not being pushed down when we join tables with 
wide records
                 Key: DRILL-2044
                 URL: https://issues.apache.org/jira/browse/DRILL-2044
             Project: Apache Drill
          Issue Type: Bug
          Components: Query Planning & Optimization
            Reporter: Rahul Challapalli
            Assignee: Jinfeng Ni


git.commit.id.abbrev=a418af1

The filter is not being pushed down according to the plan. This could either be 
a bug or expected behavior based on the optimization rules. So someone needs to 
verify that it is atleast not a bug

{code}
explain plan for select count(ws1.str_var) from widestrings_small ws1 INNER 
JOIN widestrings_small ws2 on ws1.str_fixed_null_empty=ws2.str_var_null_empty 
where ws1.tinyint_var > 120;

00-00    Screen
00-01      StreamAgg(group=[{}], EXPR$0=[COUNT($0)])
00-02        Project(str_var=[$2])
00-03          SelectionVectorRemover
00-04            Filter(condition=[>($1, 120)])
00-05              HashJoin(condition=[=($0, $3)], joinType=[inner])
00-07                Project(str_fixed_null_empty=[$2], tinyint_var=[$1], 
str_var=[$0])
00-08                  Scan(groupscan=[ParquetGroupScan 
[entries=[ReadEntryWithPath 
[path=maprfs:/drill/testdata/data-shapes/wide-columns/5000/1000rows/parquet/widestrings_small]],
 
selectionRoot=/drill/testdata/data-shapes/wide-columns/5000/1000rows/parquet/widestrings_small,
 numFiles=1, columns=[`str_fixed_null_empty`, `tinyint_var`, `str_var`]]])
00-06                Scan(groupscan=[ParquetGroupScan 
[entries=[ReadEntryWithPath 
[path=maprfs:/drill/testdata/data-shapes/wide-columns/5000/1000rows/parquet/widestrings_small]],
 
selectionRoot=/drill/testdata/data-shapes/wide-columns/5000/1000rows/parquet/widestrings_small,
 numFiles=1, columns=[`str_var_null_empty`]]])
{code}

I attached the data file used. Let me know if you have any questions



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

Reply via email to