[
https://issues.apache.org/jira/browse/PHOENIX-5169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16805560#comment-16805560
]
Lars Hofhansl commented on PHOENIX-5169:
----------------------------------------
This snug in there:
{code}
+import javax.validation.constraints.AssertFalse;
+import javax.validation.constraints.AssertTrue;
+
{code}
And it's not needed. assertFalse and assertTrue (lowercase) from junit are
already imported. Probably an accidental Eclipse import - happened to me before
;)
> Query logger is still initialized for each query when the log level is off
> --------------------------------------------------------------------------
>
> Key: PHOENIX-5169
> URL: https://issues.apache.org/jira/browse/PHOENIX-5169
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.0.0
> Reporter: jaanai
> Assignee: jaanai
> Priority: Major
> Fix For: 4.14.2, 5.1
>
> Attachments: PHOENIX-5169-master-v2.patch,
> PHOENIX-5169-master-v3.patch, PHOENIX-5169-master-v4.patch,
> PHOENIX-5169-master.patch, image-2019-02-28-10-05-00-518.png
>
>
> we will still invoke createQueryLogger in PhoenixStatement for each query
> when query logger level is OFF, which has significant throughput impacts
> under multiple threads.
> The below is jstack with the concurrent query:
> !https://gw.alicdn.com/tfscom/TB1HC3bI4TpK1RjSZFMXXbG_VXa.png|width=500,height=400!
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
