cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5149) Respect slice count even if column expire mid-request
Date Tue, 18 Jun 2013 13:59:20 GMT


Aleksey Yeschenko commented on CASSANDRA-5149:


bq. In CounterColumn.reconcile (and CounterMutation and ... in fact), we don't support expiring
columns in counter tables so it's ok to just use say Long.MIN_VALUE (which a comment why)

I know. Same with Column.getString() - it's overloaded by ExpiringColumn anyway. I was debating
with myself what to use - Long.MIN_VALUE, 0, or just System.currentTimeMillis() where it doesn't
matter, and went with System.currentTimeMillis(). Will change to 0 with a comment in both
> 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