phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-2715) Query Log
Date Sun, 08 Apr 2018 04:27:00 GMT


Josh Elser commented on PHOENIX-2715:

I pulled down the Master patch and tried that out locally. I see the SYSTEM.LOG table was
created, but the table is not getting propagated with any information. I didn't set any extra
configuration – looking at the IT, maybe I need to enable request metrics for it to work?

Maybe it's related to just using sqlline? I've been waiting a bit to see if the results are
just delayed, and that doesn't seem to be the case. I can see that the QueryLogger is created
and then stopped before I get a prompt. Additionally, I can see that there is no {{QueryLogger*}}
thread running in the sqlline jvm. I'll try to play around with this some more tmrw.

> 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