You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Xinyi Yan (Jira)" <ji...@apache.org> on 2020/10/28 02:34:00 UTC

[jira] [Updated] (PHOENIX-6009) RESULT_SET_TIME_MS includes the time spent between 2 rs.next calls.

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

Xinyi Yan updated PHOENIX-6009:
-------------------------------
    Fix Version/s:     (was: 4.16.0)
                   4.17.0
                   4.16.1

> RESULT_SET_TIME_MS includes the time spent between 2 rs.next calls.
> -------------------------------------------------------------------
>
>                 Key: PHOENIX-6009
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6009
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Rushabh Shah
>            Assignee: Rushabh Shah
>            Priority: Major
>             Fix For: 4.16.1, 4.17.0
>
>
> In current implementation, RESULT_SET_TIME_MS metric measures the time between first resultSet#next and resultSet#close call.  Assume the client is doing some expensive computations on the result set received. We will also include that time in our RESULT_SET_TIME_MS metric but technically this time was not spent on phoenix client side fetch.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)