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

["Chris Riccomini (JIRA)" <ji...@apache.org>]

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

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

bq. This will be true not just for the stores, but also out-of-the-box supported producers and consumers (HDFS, S3, etc.).

110% agree.

Other random thought: perhaps we just want to ditch LevelDB entirely? There is some risk with doing so, since RocksDB will surely have its own quirks, but I feel like it might make sense to just have one since they're basically the same thing. It's hard to justify keeping LevelDB around when RocksDB is running smoothly.

> 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
>             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.2#6252)