[jira] [Assigned] (IMPALA-7097) Print EC info in the query plan and profile

2020-06-10 Thread Sahil Takiar (Jira) 


 [ 
https://issues.apache.org/jira/browse/IMPALA-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sahil Takiar reassigned IMPALA-7097:


Assignee: Qifan Chen

> 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
>
> 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)

-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org

[jira] [Assigned] (IMPALA-7097) Print EC info in the query plan and profile

2018-06-09 Thread Tianyi Wang (JIRA) 


 [ 
https://issues.apache.org/jira/browse/IMPALA-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tianyi Wang reassigned IMPALA-7097:
---

Assignee: (was: Tianyi Wang)

> 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
>Priority: Minor
>
> 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
(v7.6.3#76005)

-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org