[jira] [Commented] (CASSANDRA-17034) CEP-11: Memtable API implementation

["Caleb Rackliffe (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-17034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17521946#comment-17521946 ] 

Caleb Rackliffe commented on CASSANDRA-17034:
---------------------------------------------

[~blambov] Not quite done with my review pass, but just wanted to clarify something about the pieces of the Memtable API that are in this Jira but only used by CASSANDRA-17240. (ex. {{ShardBoundaries}} and friends) Assuming we can resolve this issue before the 4.1 freeze, is the reason we want these items included *now* that we want to be able to plug in CASSANDRA-17240 to 4.1 builds even though it doesn't land in-tree until 5.0?

At the end of the day, CASSANDRA-17240 is going to happen, and as long as the bits we're committing up-front here aren't destabilizing, it doesn't really matter. Just doing my due diligence to make sure the patch isn't any larger than it has to be. Thoughts?

> CEP-11: Memtable API implementation
> -----------------------------------
>
>                 Key: CASSANDRA-17034
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17034
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Local/Memtable
>            Reporter: Branimir Lambov
>            Assignee: Branimir Lambov
>            Priority: Normal
>          Time Spent: 13h 40m
>  Remaining Estimate: 0h
>
> Pluggable memtable API as described in [CEP-11|https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-11%3A+Pluggable+memtable+implementations].
>  
> Initial version is already available in [this branch|https://github.com/datastax/cassandra/tree/memtable-api], and needs to be updated to the changes in trunk. Two additional features suggested by CEP reviewers are also to be implemented:
>  * Sharding support: extending the memtable owner interface to supply suitable shard boundaries that split the owned token space and are in agreement with disk boundaries.
>  * Shared read API with sstables: defining a common interface for reading partitions from memtables and sstables; this is to include filters to avoid unnecessary copying.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

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