[
https://issues.apache.org/jira/browse/SAMZA-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14153814#comment-14153814
]
Chris Riccomini commented on SAMZA-236:
---------------------------------------
Latest patch now builds against CentOS 5.6 Vagrant VMs. This appears to have
fixed the GLIBC problem that I was seeing.
I have run the RocksDB tests attached to this JIRA with the fat jar produced
from my RocksDB patch. The tests pass on Mac OSX 64-bit, Linux 32-bit Ubuntu
Trusty, Linux 32-bit CentOS 5.6, Linux 64-bit CentOS 5.6, and Linux 64-bit RHEL
6.4.
> 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.8.0
> Reporter: Chris Riccomini
> Assignee: Naveen
> Fix For: 0.8.0
>
> Attachments: SAMZA-236.diff
>
>
> 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)
