[jira] [Commented] (PHOENIX-2715) Query Log

["Andrew Purtell (JIRA)" <ji...@apache.org>]

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

Andrew Purtell commented on PHOENIX-2715:
-----------------------------------------

Great idea. It can also be useful for post hoc characterization of production workload for load generation tools that simulate production conditions (perhaps scaled) for dev and staging environments. Lots of possibilities. If you're willing to also consider this use case, then we should think about how sensitive information in queries can be masked or substituted with fake data, to avoid security and compliance issues in some environments. 

> Query Log
> ---------
>
>                 Key: PHOENIX-2715
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2715
>             Project: Phoenix
>          Issue Type: New Feature
>            Reporter: Nick Dimiduk
>
> 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
(v6.3.4#6332)