[
https://issues.apache.org/jira/browse/IMPALA-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qifan Chen resolved IMPALA-7097.
--------------------------------
Fix Version/s: Impala 4.0
Resolution: Fixed
> Print EC info in the query plan and profile
> -------------------------------------------
>
> Key: IMPALA-7097
> URL: https://issues.apache.org/jira/browse/IMPALA-7097
> Project: IMPALA
> Issue Type: Sub-task
> Components: Frontend
> Affects Versions: Impala 3.1.0
> Reporter: Tianyi Wang
> Assignee: Qifan Chen
> Priority: Minor
> Fix For: Impala 4.0
>
>
> Impala should print EC-related info in the query plan to help user understand
> the behavior and diagnose performance issues easier. The most trivial design
> would look like:
> {noformat}
> [localhost:21000] functional> explain select * from functional.alltypes;
> Query: explain select * from functional.alltypes
> +-------------------------------------------------------------+
> | Explain String |
> +-------------------------------------------------------------+
> | Max Per-Host Resource Reservation: Memory=32.00KB Threads=3 |
> | Per-Host Resource Estimates: Memory=160.00MB |
> | Codegen disabled by planner |
> | |
> | PLAN-ROOT SINK |
> | | |
> | 01:EXCHANGE [UNPARTITIONED] |
> | | |
> | 00:SCAN HDFS [functional.alltypes] |
> | partitions=24/24 files=25 size=498.41KB |
> | EC files=24 size=478.45KB |
> +-------------------------------------------------------------+
> {noformat}
> In the query profile we should at least print "EC bytes scanned" in the scan
> node.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
