[
https://issues.apache.org/jira/browse/CASSANDRA-8059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14159326#comment-14159326
]
mck edited comment on CASSANDRA-8059 at 10/4/14 10:52 PM:
----------------------------------------------------------
Looks like it should be done within each CQLStatement implementation so to a)
use the appropriate timeout settings for different cql statements, and b)
ensure clientState.hasColumnFamilyAccess(..) has been called.
was (Author: michaelsembwever):
Look like it should be done within each CqlStatement implementation so to a)
use the appropriate timeout settings for different cql statements, and b)
ensure clientState.hasColumnFamilyAccess(..) has already been called.
> CQL requests need to go through the request scheduler
> -----------------------------------------------------
>
> Key: CASSANDRA-8059
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8059
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: mck
>
> Implementing CASSANDRA-8032 it seems that no cql/cql3 requests go through the
> request scheduler. I'm guessing they never have?
> If this is to be fixed/implemented then it looks like that there's a number
> of methods in `CassandraServer` that need to call `schedule(timeout)`.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
