[
https://issues.apache.org/jira/browse/CASSANDRA-13981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17436124#comment-17436124
]
shylaja kokoori commented on CASSANDRA-13981:
---------------------------------------------
The code is under active development. The implementation has been modified to
make use of the pluggable memtable interface introduced by CEP11. We are in the
process of making the code feature complete while we wait for resolution of
following JIRAs.
CASSANDRA-17034 CEP-11: Memtable API implementation
CASSANDRA-6936 Make all byte representations of types comparable by their
unsigned byte representation only
> Enable Cassandra for Persistent Memory
> ---------------------------------------
>
> Key: CASSANDRA-13981
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13981
> Project: Cassandra
> Issue Type: New Feature
> Components: Legacy/Core
> Reporter: Preetika Tyagi
> Assignee: Preetika Tyagi
> Priority: Normal
> Fix For: 4.x
>
> Attachments: in-mem-cassandra-1.0.patch, in-mem-cassandra-2.0.patch,
> in-mem-cassandra-2.1.patch, readme.txt, readme2.1.txt, readme2_0.txt
>
>
> Currently, Cassandra relies on disks for data storage and hence it needs data
> serialization, compaction, bloom filters and partition summary/index for
> speedy access of the data. However, with persistent memory, data can be
> stored directly in the form of Java objects and collections, which can
> greatly simplify the retrieval mechanism of the data. What we are proposing
> is to make use of faster and scalable B+ tree-based data collections built
> for persistent memory in Java (PCJ: https://github.com/pmem/pcj) and enable a
> complete in-memory version of Cassandra, while still keeping the data
> persistent.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
