Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
1.4.0
-
None
-
4 node cluster CentOS
Description
Difference in query plan seen in window function query on JDK8 with below test environment, the difference being that a Project is missing after the initial Scan, the new plan looks more optimized. Should we update the expected query plan or further investigation is required ?
Java 8
MapR Drill 1.4.0 GA
JDK8
MapR FS 5.0.0 GA
Functional/window_functions/optimization/plan/pp_03.sql
Actual plan 00-00 Screen 00-01 Project(EXPR$0=[$0]) 00-02 Project($0=[$2]) 00-03 Window(window#0=[window(partition {1} order by [] range between UNBOUNDED PRECEDING and UNBOUNDED FOLLOWING aggs [SUM($0)])]) 00-04 SelectionVectorRemover 00-05 Sort(sort0=[$1], dir0=[ASC]) 00-06 Scan(groupscan=[ParquetGroupScan [entries=[ReadEntryWithPath [path=maprfs:///drill/testdata/subqueries/t1]], selectionRoot=maprfs:/drill/testdata/subqueries/t1, numFiles=1, usedMetadataFile=false, columns=[`a1`, `c1`]]]) Expected plan Screen .*Project.* .*Project.* .*Window.*range between UNBOUNDED PRECEDING and UNBOUNDED FOLLOWING aggs.* .*SelectionVectorRemover.* .*Sort.* .*Project.* .*Scan.*