[
https://issues.apache.org/jira/browse/CASSANDRA-13002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877542#comment-15877542
]
Jon Haddad commented on CASSANDRA-13002:
----------------------------------------
Sorry, I should have been more clear. I created my tables using 3.0, then
switched to trunk + this patch and tried to start the server again. I'm not
sure what needs to be done to make the schema upgrade work when the version
changes. Maybe [~iamaleksey] can point us in the right direction?
For the documentation, we should update the CQL Spec: doc/source/cql/ddl.rst.
> per table slow query times
> --------------------------
>
> Key: CASSANDRA-13002
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13002
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Jon Haddad
> Assignee: Murukesh Mohanan
> Fix For: 4.x
>
> Attachments:
> 0001-Add-per-table-slow_query_log_timeout_in_ms-property.patch,
> 0001-Add-per-table-slow_query_log_timeout_in_ms-property.patch
>
>
> 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 level.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
