[
https://issues.apache.org/jira/browse/CASSANDRA-5149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649852#comment-13649852
]
Sylvain Lebresne commented on CASSANDRA-5149:
---------------------------------------------
bq. Does CASSANDRA-4415 make this a non-issue
I don't know. I think "we'll only ever going to return less than asked columns
if there is less than asked columns" seems a reasonably semantic to have, and
we fail that here with TTL. And even if CASSANDRA-4415 ends up hiding the
problem, it's still a performance issue, because if you can't rely on the
semantic above, you'll almost always have to do one more query than would be
enough "just to be sure" (which is what getCount() does for thrift today).
So, without saying this is a big or pressing issue, I'm -1 on "wont fixing it"
in the long run.
> 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.1
>
>
> 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
