cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Brown (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-13981) Enable Cassandra for Persistent Memory
Date Tue, 30 Jan 2018 18:53:00 GMT


Jason Brown commented on CASSANDRA-13981:

[~pree] you do not have push privileges to the apache repos; that's for Apache committers.
If you can just create a branch on your own github account, and create a PR (perhaps against
the sha you based the work on), that should be enough to get started here.

> Enable Cassandra for Persistent Memory 
> ---------------------------------------
>                 Key: CASSANDRA-13981
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Preetika Tyagi
>            Assignee: Preetika Tyagi
>            Priority: Major
>             Fix For: 4.0
>         Attachments: in-mem-cassandra-1.0.patch, readme.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: and enable a complete in-memory version of Cassandra,
while still keeping the data persistent.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message