cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5149) Respect slice count even if column expire mid-request
Date Mon, 10 Jun 2013 16:19:20 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-5149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679598#comment-13679598
] 

Aleksey Yeschenko commented on CASSANDRA-5149:
----------------------------------------------

I wasn't clear enough. I'm talking about read request timestamps, not column timestamps. And
I'm saying that to transfrom is not always correct, in the context of 5149. But *not to* transfrom
is perfectly all right.
                
> Respect slice count even if column expire mid-request
> -----------------------------------------------------
>
>                 Key: CASSANDRA-5149
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5149
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 0.7.0
>            Reporter: Sylvain Lebresne
>            Assignee: Aleksey Yeschenko
>             Fix For: 2.0
>
>
> This is a follow-up of CASSANDRA-5099.
> If a column expire just while a slice query is performed, it is possible for replicas
to count said column as live but to have the coordinator seeing it as dead when building the
final result. The effect that the query might return strictly less columns that the requested
slice count even though there is some live columns matching the slice predicate but not returned
in the result.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message