You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Jay Kreps (JIRA)" <ji...@apache.org> on 2015/01/31 04:19:35 UTC
[jira] [Commented] (SAMZA-256) Provide in-memory data store
implementation
[ https://issues.apache.org/jira/browse/SAMZA-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14299618#comment-14299618 ]
Jay Kreps commented on SAMZA-256:
---------------------------------
Hey [~criccomini] and [~cpsoman] Any reason this in memory map is doing serialization? The primary advantage of an in-memory store versus a fully cached leveldb/rocksdb would seem to be avoiding the serialization, right?
> Provide in-memory data store implementation
> -------------------------------------------
>
> Key: SAMZA-256
> URL: https://issues.apache.org/jira/browse/SAMZA-256
> Project: Samza
> Issue Type: Improvement
> Components: kv
> Affects Versions: 0.6.0
> Reporter: Jakob Homan
> Assignee: Chinmay Soman
> Fix For: 0.8.0
>
> Attachments: samza_256.patch, samza_256_1.patch, samza_256_2.patch
>
>
> The sole current kv store, LevelDbKeyValueStore, works well when the amount of data to be stored is prohibitively large to keep it all in memory. However, in cases where the state is small enough to comfortably fit in whatever memory is available, it would be better to provide an in-memory implementation. This can be backed by either a native Java class, or perhaps a Guava class, if that is found to scale better (or, of course, the backing implementation could be configurable).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)