Avi Bryant
Avi Bryant
This seems to overlap with my (sadly abandoned) UpdateableStore PR, right? https://github.com/twitter/storehaus/pull/119
I'm still interested but don't actively need it right now, so I'm in no rush. What do you think is the minimal TODO to make it worth merging?
Relevant: https://github.com/avibryant/rdb
I'm +1 on this thread. Especially on having a write-only abstraction - I miss Mergeable (but I think the semantics don't need to be that well-defined, ie, if it wants...
Agree with @softprops, but just to make a related point: I think the one big use case of this is for clients who only need a Writable to be able...
Semantically they don't, but I think that given the rest of Storehaus has a K,V, we should keep that here for consistency. I was imagining StdoutWritable looking sorta like this:...
Hm, I'm not following. The semantics I'm looking for are an atomic read->modify->write. For Redis it would look something like this (with some kind of configurable retry logic, maybe): ```...
Ah cool, didn't know memcache had CAS. I'll take this.
From the point of view of reasoning about consistency, it may be that some combination of MergeableStore and UpdatableStore are the right level of abstraction; that is, you may want...
.. actually I guess it would probably want to be a whole kinesis planner rather than using storm.