[
https://issues.apache.org/jira/browse/CASSANDRA-5149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679220#comment-13679220
]
Aleksey Yeschenko commented on CASSANDRA-5149:
----------------------------------------------
There is another method that is affected - ExpiringColumn.create() that returns
either a DeletedColumn or an ExpiringColumn instance, called by
ColumnSerializer.deserializeColumnBody(). Now, we already do pass expireBefore
to it as a parameter (in a limited way) and it's not (was not) difficult to
make it be derived from read requests' timestamp. Except in one case - row
cache deserialization. The required modifications go beyond the need for Cache
API change and I haven't found a good way to deal with it.
Is there any change we actually will get rid of row cache in 2.0?
> 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
