cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5149) Respect slice count even if column expire mid-request
Date Mon, 10 Jun 2013 15:37:22 GMT


Sylvain Lebresne commented on CASSANDRA-5149:

bq. But I'm afraid it's not enough

I'm not sure I understand the case you are talking about. Whether or not ExpiringColumn.create()
decides to return a deleted column or not, it still returns a column, so this should have
no impact whatsoever on anything timestamp related. I.e. the code will treat an ExpiringColumn
that is expired exactly as a deleted column, so it should always be safe to not transform
an expired column to a DeletedColumn, even if it's only in parts of the code.

But it could be I just don't understand your example.
> Respect slice count even if column expire mid-request
> -----------------------------------------------------
>                 Key: CASSANDRA-5149
>                 URL:
>             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:

View raw message