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

Posted to commits@cassandra.apache.org by "ZhaoYang (Jira)" <ji...@apache.org> on 2020/04/19 13:50:00 UTC

[jira] [Updated] (CASSANDRA-14586) Performant range containment check for SSTables

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

ZhaoYang updated CASSANDRA-14586:
---------------------------------
    Resolution: Duplicate
        Status: Resolved  (was: Open)

Marked it as duplicate of CASSANDRA-15657. Thanks

> Performant range containment check for SSTables
> -----------------------------------------------
>
>                 Key: CASSANDRA-14586
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14586
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Legacy/Streaming and Messaging
>            Reporter: Dinesh Joshi
>            Assignee: Dinesh Joshi
>            Priority: Normal
>              Labels: Performance
>
> Related to CASSANDRA-14556, we would like to make the range containment check performant. Right now we iterate over all partition keys in the SSTables and determine the eligibility for Zero Copy streaming. This ticket is to explore ways to make it performant by storing information in the SSTable's Metadata.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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