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 Mon, 02 Apr 2018 20:55:00 GMT


Andrew Purtell commented on PHOENIX-2715:

Since my query is being ignored, I am -1 on this patch until we discuss it. This is a binding

Please respond:
{quote}Is it possible to set a flag or a configuration variable so bind parameter logging
can be left out?
Reason I ask is the query log feature will otherwise not be useful in many environments with
compliance requirements for personally identifiable information (commonly abbreviated as PII).
Assuming a coder can isolate PII to bind variables, which is a reasonable tradeoff, It doesn't
seem hard to do this. So why not at least consider it? Seems easy to make logging of bind
parameter information configurable.

> 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