[
https://issues.apache.org/jira/browse/CASSANDRA-20923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-20923:
-------------------------------------------
Fix Version/s: 5.0.x
5.x
> Segregate SAI's query metrics per query type
> --------------------------------------------
>
> Key: CASSANDRA-20923
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20923
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Feature/SAI
> Reporter: Michael Semb Wever
> Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> SAI's tracks query metrics providing info about latency, partition reads,
> filtered rows, etc. These metrics are for all the SAI queries for a certain
> table. When we see problems in queries, for example a high latency, questions
> that can usually come next are what query is producing this high latency? Are
> there vector queries? Are queries for a single partition? In that case, what
> is the latency of those queries? How many rows are they selecting? To answer
> those questions, I think it can be useful to track metrics for specific types
> of query.
> Tracking is done in a {{TableQueryMetrics}} associated to the table.
> This PR only adds a few type of queries: filtering, top-k, single-partition
> and range queries. If we need new types in the future, this patch should make
> it easy to add separate metrics for them, possibly with an one-liner.
> The general query metrics remain untouched, this PR only adds new ones.
> More background info from downstream work in
> https://github.com/datastax/cassandra/pull/1969 and
> https://github.com/datastax/cassandra/pull/2015
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
