cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-13050) ReadCommand.CheckForAbort not monitoring CQL rows for range queries
Date Fri, 23 Dec 2016 01:46:58 GMT


Stefania updated CASSANDRA-13050:
       Resolution: Fixed
    Fix Version/s:     (was: 3.x)
           Status: Resolved  (was: Ready to Commit)

Thank you for the review and for following up on the tests.

Committed to the 3.11 branch as 84b1725fb4c4cba4fdb94f2abdb66656a4c66ae1 and merged into 3.X
and trunk.

> ReadCommand.CheckForAbort not monitoring CQL rows for range queries
> -------------------------------------------------------------------
>                 Key: CASSANDRA-13050
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Local Write-Read Paths
>            Reporter: Stefania
>            Assignee: Stefania
>             Fix For: 3.10
> -If I understood the iterator transformations introduced by CASSANDRA-9975 correctly,-
should apply itself before returning a partition. At the moment it is applied to row iterators
for single command partitions, but for range queries -I think- it only monitors the query
progress when a new partition is iterated, not when a new row is iterated. So for large partitions,
we may fail to log a query as slow, or fail to abort it if the RPC timeout is exceeded.

This message was sent by Atlassian JIRA

View raw message