Hiya,

I wanted to share this little design doc with you about some feature work we've been thinking about. The following is a Google doc in which anyone should be allowed to comment. Feel free to comment there, or here on the thread.

https://s.apache.org/phoenix-query-log

The high-level goal is to create a construct in which Phoenix clients will automatically serialize information about the queries they run to a table for retrospective analysis. Ideally, this information would be stored in a Phoenix table. We want this data to help answer questions like:

* What queries are running against my system
* What specific queries started between 535AM and 620AM two days ago
* What queries are user "bob" running
* Are my user's queries effectively using the indexes in the system

Anti-goals for include:

* Cluster impact (computation/memory) usage of a query
* Query performance may be slowed to ensure all data is serialized
* A third-party service dedicated to ensuring query info is serialized (in the event of client failure)

Take a look at the document and let us know what you think please. I'm happy to try to explain this in greater detail.

- Josh (on behalf of myself, Ankit, Rajeshbabu, and Sergey)

Reply via email to