[
https://issues.apache.org/jira/browse/CASSANDRA-5149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13685616#comment-13685616
]
Aleksey Yeschenko commented on CASSANDRA-5149:
----------------------------------------------
Pushed the fourth commit to the same branch.
- Removed Column.isMarkedForDelete/0 and most similar methods (including
QueryFilter getXFilter helper methods)
- RowIteratorFactory/System.currentTimeMillis() - done.
- CFS.filterColumnFamily() was the only place where I could get rid of passing
gcBefore explicitly - thanks for catching that. In
IDiskAtomFilter.collectReducedColumns() timestamp and gcbefore are sometimes
unrelated (with Integer.MIN_VALUE passed as gcBefore, intentionally). Same goes
for CFS.collateOnDiskAtom(). Usually it's either because of either compaction
or the row cache.
> 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
