[
https://issues.apache.org/jira/browse/PHOENIX-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16419840#comment-16419840
]
Josh Elser commented on PHOENIX-2715:
-------------------------------------
{code:java}
+ public static final String DEFAULT_LOGGING_LEVEL = "DEBUG";{code}
Wondering if we want this to be INFO, or even OFF, by default. Not sure..
{code:java}
+ BIND_PARAMETERS_I(BIND_PARAMETERS,QueryLogState.STARTED,
LogLevel.INFO,PVarchar.INSTANCE),{code}
Wondering if this should be DEBUG. I would guess that, in most cases, we can
understand the intent of a query without the parameters being explicitly
present?
Going to try this out locally.
> 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
> Attachments: PHOENIX-2715.patch, PHOENIX-2715_master.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)
