[ 
https://issues.apache.org/jira/browse/IMPALA-13137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17852746#comment-17852746
 ] 

Surya Hebbar commented on IMPALA-13137:
---------------------------------------

The duration needed to fetch the first row is already present in the
query state record. This timestamp has to be found by matching the label
"First row fetched" within the query state record's 'event_sequence'.

The time taken for the client to fetch all rows is monitored by
the "ClientFetchWaitTimer" in client request state. To incorporate this
into the query state record, the following new attribute has been added.
* client_fetch_wait_time_ns  

In order to constantly retrieve and update this value, a new method has
been added to expose the private counter holding "ClientFetchWaitTimer".

The duration for both these columns is printed in human readable format,
after converting from nanoseconds.

Tips for the two additional columns have also been added to the queries
page.

> Add additional client fetch metrics columns to the queries page
> ---------------------------------------------------------------
>
>                 Key: IMPALA-13137
>                 URL: https://issues.apache.org/jira/browse/IMPALA-13137
>             Project: IMPALA
>          Issue Type: New Feature
>          Components: Backend, be
>            Reporter: Surya Hebbar
>            Assignee: Surya Hebbar
>            Priority: Major
>         Attachments: completed_query.png, in_flight_query_1.png, 
> in_flight_query_2.png, in_flight_query_3.png
>
>
> For helping users to better understand query execution times,  it would be 
> helpful to add the following columns on the queries page.
> * First row fetched time - Time taken for the client to fetch the first row
> * Client fetch wait time - Time taken for the client to fetch all rows
> Additional details -
> https://jira.cloudera.com/browse/DWX-18295



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to