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 00:09:20 GMT


Sylvain Lebresne commented on CASSANDRA-5149:

Can't we create a version of ExpiringColumn.create() that never transform a DeletedColumn
to an ExpiringColumn and use that for cache deserialization (or say do that when expireBefore
is negative and pass -1 for expireBefore in the row cache code).

Because that behavior of ExpiringColumn.create() is really just an optimization. It would
be ok to never transform expired columns to deleted ones from a correction point of view.
> 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