You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2014/07/09 18:43:04 UTC

[jira] [Comment Edited] (PHOENIX-1062) A SQL Trimmer for log sql execute times

    [ https://issues.apache.org/jira/browse/PHOENIX-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056430#comment-14056430 ] 

James Taylor edited comment on PHOENIX-1062 at 7/9/14 4:41 PM:
---------------------------------------------------------------

I don't think universally every one would want to normalize their queries in this way. Sometimes you may want to track down queries that aren't parameterized so that you can parameterize them. I'm fine with adding more logging that helps you, though.


was (Author: jamestaylor):
I don't think universally every one would want to normalize their queries in this way.

> 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)