Aman Sinha created DRILL-1334:
---------------------------------
Summary: Sequence and numbering of operators in query profile does
not match physical plan
Key: DRILL-1334
URL: https://issues.apache.org/jira/browse/DRILL-1334
Project: Apache Drill
Issue Type: Bug
Affects Versions: 0.4.0
Reporter: Aman Sinha
The query profile for the fragment 2 below shows operators 0 to 4 (Parquet
Group Scan is 0 and top Project is 4). This does not match the physical plan
which shows Parquet Group Scan as operator 5 and the top Project as operator id
1. We should make the profile consistent with the plan.
{code:sql}
#2 - Op 0 PARQUET_ROW_GROUP_SCAN
#2 - Op 1 PROJECT
#2 - Op 2 SELECTION_VECTOR_REMOVER
#2 - Op 3 FILTER
#2 - Op 4 PROJECT
{code}
{code:sql}
00-00 Screen
00-01 StreamAgg(group=[{}], EXPR$0=[COUNT()])
00-02 UnionExchange
01-01 Project($f0=[0])
01-02 HashAgg(group=[{0, 1}])
01-03 HashToRandomExchange(dist0=[[$0]], dist1=[[$1]])
02-01 Project(sssk=[$0], ssik=[$1])
02-02 SelectionVectorRemover
02-03 Filter(condition=[AND(>=($2, 2451911), <=($2,
2452275))])
02-04 Project(ss_store_sk=[$1], ss_item_sk=[$2],
ss_sold_date_sk=[$0])
02-05 Scan(groupscan=[ParquetGroupScan
[entries=[ReadEntryWithPath [path=maprfs:/tmp/store_sales]],
selectionRoot=/tmp/store_sales, columns=[SchemaPath [`ss_store_sk`], SchemaPath
[`ss_item_sk`], SchemaPath [`ss_sold_date_sk`]]]])
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
