Quanlong Huang created IMPALA-14941:
---------------------------------------
Summary: ExecSummary shows 0 output rows under SUBPLAN node
Key: IMPALA-14941
URL: https://issues.apache.org/jira/browse/IMPALA-14941
Project: IMPALA
Issue Type: Bug
Reporter: Quanlong Huang
Assignee: Quanlong Huang
It's misleading that plan nodes under SUBPLAN always show 0 output rows in the
profile, E.g. for this query
{code:sql}
select id, unnest(arr1) from functional_parquet.complextypes_arrays;{code}
the ExecSummary is
{noformat}
+---------------------------+--------+-------+----------+----------+-------+------------+----------+---------------+--------------------------------------------------+
| Operator | #Hosts | #Inst | Avg Time | Max Time | #Rows |
Est. #Rows | Peak Mem | Est. Peak Mem | Detail
|
+---------------------------+--------+-------+----------+----------+-------+------------+----------+---------------+--------------------------------------------------+
| F01:ROOT | 1 | 1 | 67.58us | 67.58us | |
| 4.02 MB | 4.00 MB |
|
| 05:EXCHANGE | 1 | 1 | 14.76us | 14.76us | 22 |
13.51K | 16.00 KB | 291.87 KB | UNPARTITIONED
|
| F00:EXCHANGE SENDER | 1 | 1 | 41.14us | 41.14us | |
| 230 B | 112.00 KB |
|
| 01:SUBPLAN | 1 | 1 | 0ns | 0ns | 0 |
13.51K | 29.00 KB | 0 B |
|
| |--04:NESTED LOOP JOIN | 1 | 1 | 44.18us | 44.18us | 0 | 10
| 24.00 KB | 16 B | CROSS JOIN
|
| | |--02:SINGULAR ROW SRC | 1 | 1 | 0ns | 0ns | 0 | 1
| 0 B | 0 B |
|
| | 03:UNNEST | 1 | 1 | 6.48us | 6.48us | 0 | 10
| 0 B | 0 B |
functional_parquet.complextypes_arrays.arr1 arr1 |
| 00:SCAN HDFS | 1 | 1 | 56.55ms | 56.55ms | 11 |
1.35K | 57.04 KB | 32.00 MB | functional_parquet.complextypes_arrays
|
+---------------------------+--------+-------+----------+----------+-------+------------+----------+---------------+--------------------------------------------------+{noformat}
"#Rows" of "01:SUBPLAN", "04:NESTED LOOP JOIN", "02:SINGULAR ROW SRC" and
"03:UNNEST" are all 0.
This is harmful for HBO since historical stats will show these plan nodes have
no output, which is incorrect.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
