cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Murukesh Mohanan (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-13002) per table slow query times
Date Mon, 06 Feb 2017 04:00:43 GMT


Murukesh Mohanan updated CASSANDRA-13002:
         Assignee: Murukesh Mohanan
    Fix Version/s: 4.x
           Status: Patch Available  (was: Open)

I have implemented this by adding a table property with the same name as the global one {{slow_query_log_timeout_in_ms}},
which overrides the global one if it is not negative. So, with this, if we wanted to:

- use a different value (say 200ms) for a table
 ALTER TABLE with slow_query_log_timeout_in_ms = 200;
- disable it for a table
 ALTER TABLE with slow_query_log_timeout_in_ms = 0;
- go back to using the global value:
 ALTER TABLE with slow_query_log_timeout_in_ms = -1;


> per table slow query times
> --------------------------
>                 Key: CASSANDRA-13002
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Jon Haddad
>            Assignee: Murukesh Mohanan
>             Fix For: 4.x
> CASSANDRA-12403 made it possible to log slow queries, but the time specified is a global
one.  This isn't useful if we know different tables have different access patterns, as we'll
end up with a lot of noise.  We should be able to override the slow query time at a per table

This message was sent by Atlassian JIRA

View raw message