[
https://issues.apache.org/jira/browse/SAMZA-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058040#comment-14058040
]
Jakob Homan commented on SAMZA-256:
-----------------------------------
{noformat}jhoman-mn1:samza-kv jhoman$ tree
.
├── samza-kv_2.10.iml
└── src
└── main
├── java
│ └── org
│ └── apache
│ └── samza
│ └── storage
│ └── kv
│ ├── Entry.java
│ ├── KeyValueIterator.java
│ └── KeyValueStore.java
└── scala
└── org
└── apache
└── samza
└── storage
└── kv
├── BaseKeyValueStorageEngineFactory.scala
├── CachedStore.scala
├── CachedStoreMetrics.scala
├── KeyValueStorageEngine.scala
├── KeyValueStorageEngineMetrics.scala
├── KeyValueStoreMetrics.scala
├── LoggedStore.scala
├── LoggedStoreMetrics.scala
├── NullSafeKeyValueStore.scala
├── SerializedKeyValueStore.scala
└──
SerializedKeyValueStoreMetrics.scala{noformat}
Just noticed this is our first non-samza-test mix of Scala and Java. I'm cool
with that, but worth pointing out.
> 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.2#6252)
