[
https://issues.apache.org/jira/browse/PHOENIX-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056002#comment-14056002
]
jay wong commented on PHOENIX-1062:
-----------------------------------
[~jamestaylor]
Yes I used to log sql execute. In my code I write it in
org.apache.phoenix.coprocessor.ScanRegionObserver#doPostScannerOpen
{code}
logger.trace("The SQL which get scanner is :" + SQLTrimmer.trim(sql));
{code}
So If anyone have the same statistics as me. will need it. else It does not
needed.
> A SQL Trimmer for log sql execute times
> ---------------------------------------
>
> Key: PHOENIX-1062
> URL: https://issues.apache.org/jira/browse/PHOENIX-1062
> Project: Phoenix
> Issue Type: New Feature
> Affects Versions: 3.0.0
> Reporter: jay wong
> Priority: Critical
> Fix For: 3.1
>
> Attachments: SQLTrimmer.java
>
>
> If we need a statistics that which sql execute times
> just like : select a,b,c from table1 where d=13 and e='abc' limit 20;
> but the condition value is not needed because of overlap
> so the will be trim as : select a,b,c from table1 where d=? and e=? limit ?;
> Now the tool fix it
--
This message was sent by Atlassian JIRA
(v6.2#6252)
