[
https://issues.apache.org/jira/browse/PHOENIX-4854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586967#comment-16586967
]
Hudson commented on PHOENIX-4854:
---------------------------------
FAILURE: Integrated in Jenkins build PreCommit-PHOENIX-Build #1995 (See
[https://builds.apache.org/job/PreCommit-PHOENIX-Build/1995/])
PHOENIX-4854 Make LoggingPhoenixResultSet idempotent when logging
(karanmehta93: rev 76e6f9d9f5290cc44881a774869ed97f013302d4)
* (edit)
phoenix-core/src/it/java/org/apache/phoenix/monitoring/PhoenixLoggingMetricsIT.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/jdbc/LoggingPhoenixResultSet.java
> 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)
