You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Chris Riccomini (JIRA)" <ji...@apache.org> on 2014/09/23 23:43:34 UTC

[jira] [Commented] (SAMZA-236) Switch samza-kv to use RocksDB

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

Chris Riccomini commented on SAMZA-236:
---------------------------------------

I've opened up a [Github issue|https://github.com/facebook/rocksdb/issues/308] with RocksDB to track their Maven publication.

> Switch samza-kv to use RocksDB
> ------------------------------
>
>                 Key: SAMZA-236
>                 URL: https://issues.apache.org/jira/browse/SAMZA-236
>             Project: Samza
>          Issue Type: Bug
>          Components: kv
>    Affects Versions: 0.6.0
>            Reporter: Chris Riccomini
>            Assignee: Naveen
>             Fix For: 0.8.0
>
>
> The samza-kv implementation is currently using LevelDB. RocksDB seems to have a number of interesting options that would be useful to Samza:
> # Ability to swap out skip list for a faster implementation when restoring data from a changelog stream.
> # Ability to disable compaction during changelog stream restoration.
> # Ability to have a single level (or single SST) rather than multiple levels in order to reduce read amplification.
> # A merge operation for doing lazy read-modify-write during compaction.
> And a lot more.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)