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

Erick Ramirez updated CASSANDRA-17761:
--------------------------------------
    Status: Changes Suggested  (was: Review In Progress)

The following elements need to be fixed:

bq. One of the new features of Apache Cassandra 4.1, introduced with [Cassandra 
Enhancement Proposal (CEP) 11|https://cwiki.apache.org/confluence/x/0goBCw], is 
support for alternative memtable implementations.

bq. where the '{{{color:#DE350B}sharded{color}}}' configuration is defined in 
cassandra.yaml as

bq. A Trie-based memtable 
([CEP-19|https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-19%3A+Trie+memtable+implementation]/https://issues.apache.org/jira/browse/CASSANDRA-17240[CASSANDRA-17240]),

> WEBSITE - July 2022 blog "Apache Cassandra 4.1 Features: Pluggable Memtable 
> Implementations"
> --------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-17761
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17761
>             Project: Cassandra
>          Issue Type: Task
>          Components: Documentation/Blog
>            Reporter: Diogenese Topper
>            Assignee: Erick Ramirez
>            Priority: Normal
>              Labels: pull-request-available
>             Fix For: 4.1.x
>
>
> This ticket is to capture the work associated with publishing the July 2022 
> blog "Apache Cassandra 4.1 Features: Pluggable Memtable Implementations"
> If this blog cannot be published by the *July 21, 2022 publish date*, please 
> contact me, suggest changes, or correct the date when possible in the pull 
> request for the appropriate time that the blog will go live (on both the 
> blog.adoc and the blog post's file).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to