storehaus
storehaus copied to clipboard
twitter
Storehaus is a library that makes it easy to work with asynchronous key value stores
Came up in https://github.com/twitter/storehaus/pull/225
It is clearly broken for a Mergeable to implement merge by read + write but issue several outstanding reads and ignore the others on write. There are a few solutions...
something like: ``` scala trait CASStore[T:Equiv, K, V] { def get(k: K): Future[(V, T)] // returns the token immediately before // and the value. If the result equiv(Token, T), then...
Would be very useful for scalding + summingbird jobs to have cascading taps to read and write storehaus stores: Writing a custom Tap is not too much work. You can...
We could use cassie which is built on finagle: https://github.com/twitter/cassie Configure your cluster, keyspace, column family and pass it to the storehaus wrapper.
``` scala trait PagingReadableStore[K, V] extends ReadableStore[K,Spool[V]] // see: https://github.com/twitter/util/blob/master/util-core/src/main/scala/com/twitter/concurrent/Spool.scala //combinator: object PagingReadableStore { // C is some cursor type def from[K,V,C](readable: ReadableStore[(K,C), (V,C)])(nextPage: C => C): PagingReadableStore[K,V] // do...
If a store could produce an iterator over its pairs it'd be possible to write a `StorehausInputFormat` and consume storehaus data from scalding. ``` scala trait IterableStore[-K, V] extends ReadableStore[K,...
Some example code here: https://github.com/azymnis/scalafish/blob/master/src/main/scala/org/zymnis/scalafish/zookeeper/Client.scala#L93 Might be good to use util-zk too: https://github.com/twitter/util/tree/master/util-zk/src/main/scala/com/twitter/zk I guess you have two stores here: Data at nodes: K = Path, V = (Data(Array[Byte]), Stat)...
Opposite of this: https://github.com/twitter/storehaus/blob/develop/storehaus-core/src/main/scala/com/twitter/storehaus/UnpivotedStore.scala#L28