phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-2715) Query Log
Date Tue, 03 Apr 2018 03:42:00 GMT


Andrew Purtell commented on PHOENIX-2715:

Thank you. My mistake for not seeing the earlier comment. Didn't see it in the patch I looked
at, but may have missed a different log level. Veto rescinded. Separate log line would work.
We don't need a server side configuration. Compliance is usually a cooperative effort undertaken
by the whole organization. As long as it is possible to apply the controls, and there is a
documented process to confirm the controls are in place (eg correctly configured log levels),
and there is documentation the process was followed, this should be good. Certainly for a
first version of the feature. 

> Query Log
> ---------
>                 Key: PHOENIX-2715
>                 URL:
>             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

View raw message