You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Ankit Singhal (JIRA)" <ji...@apache.org> on 2018/03/28 14:02:00 UTC
[jira] [Updated] (PHOENIX-2715) Query Log
[ https://issues.apache.org/jira/browse/PHOENIX-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ankit Singhal updated PHOENIX-2715:
-----------------------------------
Attachment: PHOENIX-2715.patch
> Query Log
> ---------
>
> Key: PHOENIX-2715
> URL: https://issues.apache.org/jira/browse/PHOENIX-2715
> Project: Phoenix
> Issue Type: New Feature
> Reporter: Nick Dimiduk
> Priority: Major
> Attachments: PHOENIX-2715.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)