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

Lars Hofhansl edited comment on PHOENIX-2715 at 5/25/18 2:57 AM:
-----------------------------------------------------------------

The default is supposed to the OFF, right?

I just tried with a vanilla build from Phoenix' master branch and I see 
SYSTEM.LOG is being written to.

Looking at the code I see the default *is* OFF, so something is not working 
right, unless I misunderstood something.

Everything but OFF is a bad default, IMHO.

[~an...@apache.org]


was (Author: lhofhansl):
The default is supposed to the OFF, right?

I just true with a vanilla build from Phoenix' master branch and I see 
SYSTEM.LOG is being written to.

Looking at the code I see the default *is* OFF, so something is not working 
right, unless I misunderstood something.

Everything but OFF is a bad default, IMHO.

[~an...@apache.org]

> Query Log
> ---------
>
>                 Key: PHOENIX-2715
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2715
>             Project: Phoenix
>          Issue Type: New Feature
>            Reporter: Nick Dimiduk
>            Assignee: Ankit Singhal
>            Priority: Major
>             Fix For: 4.14.0, 5.0.0
>
>         Attachments: PHOENIX-2715.patch, PHOENIX-2715_master.patch, 
> PHOENIX-2715_master_V1.patch, PHOENIX-2715_master_V2.patch
>
>
> One useful feature of other database systems is the query log. It allows the 
> DBA to review the queries run, who's run them, time taken, &c. This serves 
> both as an audit and also as a source of "ground truth" for performance 
> optimization. For instance, which columns should be indexed. It may also 
> serve as the foundation for automated performance recommendations/actions.
> What queries are being run is the first piece. Have this data tied into 
> tracing results and perhaps client-side metrics (PHOENIX-1819) becomes very 
> useful.
> This might take the form of clients writing data to a new system table, but 
> other implementation suggestions are welcome.



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

Reply via email to