[
https://issues.apache.org/jira/browse/CASSANDRA-5149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13585937#comment-13585937
]
Sylvain Lebresne commented on CASSANDRA-5149:
---------------------------------------------
Actually, this is not as free of a lunch as it sound. We cannot really force
non-expired ExpiringColumn to Column, because we need to return the expiring
time to the client. So in practice, we would need to either add a dontExpire
flag for ExpiringColumn or a special Column+TTL column type for just that
purpose. Any of those will have impact on the inter-node protocol (and at the
column serialization, where we don't yet handle versions well (because we never
really had to)).
And if that's not significantly simpler, I think I prefer the expireBefore
solution because that feels less hacky to me in that it fixes the issue of
having column expire at uncontrolled times more generally (this is also how we
deal with it in LazilyCompactedRow).
> 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
> 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
