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

Posted to dev@phoenix.apache.org by "Karan Mehta (JIRA)" <ji...@apache.org> on 2018/08/20 22:17:00 UTC

[jira] [Resolved] (PHOENIX-4854) Make LoggingPhoenixResultSet idempotent when logging metrics

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

Karan Mehta resolved PHOENIX-4854.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 5.1.0
                   4.15.0

Committed to master branch as well (All unit tests and metrics IT pass)

> Make LoggingPhoenixResultSet idempotent when logging metrics
> ------------------------------------------------------------
>
>                 Key: PHOENIX-4854
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4854
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Karan Mehta
>            Assignee: Karan Mehta
>            Priority: Major
>             Fix For: 4.15.0, 5.1.0
>
>
> ResultSet close method can be called multiple times and LoggingResultSet object tries to call PhoenixMetricsLog methods every single time. These per query metrics don't get cleared up, rather they are all at "0" value once they are consumed and reset. This Jira is an enhancement to bring the idempotency in the class.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)