You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Benedict (JIRA)" <ji...@apache.org> on 2015/07/17 12:13:04 UTC

[jira] [Resolved] (CASSANDRA-9835) Restore collectTimeOrderedData behaviour post-8099

     [ https://issues.apache.org/jira/browse/CASSANDRA-9835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benedict resolved CASSANDRA-9835.
---------------------------------
    Resolution: Invalid

> Restore collectTimeOrderedData behaviour post-8099
> --------------------------------------------------
>
>                 Key: CASSANDRA-9835
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9835
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Benedict
>             Fix For: 3.0.x
>
>
> AFAICT, we no longer prune the sstables we iterate once we know we've satisfied a query. This is not only still possible, but possible in more scenarios (since we can do it for any single CQL-row lookup).
> Affected workloads may have noticeably degraded behaviour, and this will impact CASSANDRA-6477.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)