[ https://issues.apache.org/jira/browse/PHOENIX-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16434134#comment-16434134 ]
Hudson commented on PHOENIX-2715: --------------------------------- FAILURE: Integrated in Jenkins build PreCommit-PHOENIX-Build #1828 (See [https://builds.apache.org/job/PreCommit-PHOENIX-Build/1828/]) PHOENIX-2715 Query Log (addendum) Fix old com.lmax.disruptor dependency (ankitsinghal59: rev d48518bc2ddea3f4c6cd9ef5a6c2504b65255da2) * (edit) phoenix-core/pom.xml * (edit) phoenix-flume/pom.xml * (edit) phoenix-kafka/pom.xml > Query Log > --------- > > Key: PHOENIX-2715 > URL: https://issues.apache.org/jira/browse/PHOENIX-2715 > Project: Phoenix > Issue Type: New Feature > Reporter: Nick Dimiduk > Assignee: Ankit Singhal > Priority: Major > Fix For: 4.14.0, 5.0.0 > > Attachments: PHOENIX-2715.patch, PHOENIX-2715_master.patch, > PHOENIX-2715_master_V1.patch, PHOENIX-2715_master_V2.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)