[
https://issues.apache.org/jira/browse/CASSANDRA-5149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13551181#comment-13551181
]
Sylvain Lebresne commented on CASSANDRA-5149:
---------------------------------------------
As said on CASSANDRA-5099, the only good way to fix this that I can see right
now would be to have the coordinator determine an expireBefore value (the
current time at the beginning of the request) and use that exclusively during
the query to decide whether a query is expired or not (similar to what we do
for LazilyCompactedRow but at the scale of the query).
Unfortunately, this means shipping that expireBefore value to replicas with the
query and that implies a inter-node protocol change, which make this only
viable for 2.0 now. Hence the 'fix version'. Of course if we can find a
solution that don't require protocol change, then great.
> 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
