cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "DOAN DuyHai (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-13476) RocksDB based storage engine
Date Mon, 02 Oct 2017 17:52:01 GMT


DOAN DuyHai commented on CASSANDRA-13476:

A stupid question but when using RockDB, how can we support all the CQL semantics (like collections,
clustering, TTL, LWT, SASI, MV, UDF/UDA ...) ?

I don't feel like having different storage engines supporting different subsets of CQL features,
ending up with a matrix of supported/unsupported features.

Also, I guess that implementing some features like collections or counters will yield different
performance characteristics when switching between different storage engines. It would be
nice that it is clearly indicated not to get the users by surprise

Also, compaction strategies will also be per-storage engine specific right ? 

> RocksDB based storage engine
> ----------------------------
>                 Key: CASSANDRA-13476
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Dikang Gu
> As I mentioned in CASSANDRA-13474, we got huge P99 read latency gain from the RocksDB
integration experiment.
> After we make the existing storage engine to be pluggable, we want to implement a RocksDB
based storage engine, which can support existing Cassandra data model, and provide better
and more predictable performance.
> The effort will include but not limited to:
> 1. Wide column support on RocksDB
> 2. Streaming support on RocksDB
> 3. RocksDB instances management
> 4. Nodetool support
> 5. Metrics and monitoring
> 6. Counter support on RocksDB

This message was sent by Atlassian JIRA

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

View raw message