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

Posted to commits@cassandra.apache.org by "Blake Eggleston (JIRA)" <ji...@apache.org> on 2019/05/20 19:33:00 UTC

[jira] [Updated] (CASSANDRA-14516) filter sstables by min/max clustering bounds during reads

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

Blake Eggleston updated CASSANDRA-14516:
----------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Open)

Thanks for looking into this [~n.v.harikrishna]. Sorry for the false alarm.

> filter sstables by min/max clustering bounds during reads
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-14516
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14516
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Legacy/Local Write-Read Paths
>            Reporter: Blake Eggleston
>            Assignee: Venkata Harikrishna Nukala
>            Priority: Normal
>             Fix For: 4.0
>
>
> In SinglePartitionReadCommand, we don't filter out sstables whose min/max clustering bounds don't intersect with the clustering bounds being queried. This causes us to do extra work on the read path.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org