[
https://issues.apache.org/jira/browse/SAMZA-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13985958#comment-13985958
]
Chris Riccomini commented on SAMZA-236:
---------------------------------------
Taking this one step farther, I'd like to think about separating
samza-kv-leveldb/samza-kv-rocksdb into their own subprojects. This will
separate dependencies between the two projects. Not entirely sold on the idea,
but I'm not wild about putting LevelDB and RocksDB implementations into the
subproject either. It's worth thinking through.
> 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)
