Riak maintains a single value per key and provides mechanisms (vector clocks) to detect/resolve conflicting values. In the proposed use case the multiple copies would overwrite each other and Riak, by default, would return a single value for a requested key.
Behind the scenes Riak determines the appropriate value per key using vector clocks. More information about vector clocks is available here: http://blog.basho.com/2010/01/29/why-vector-clocks-are-easy/ http://blog.basho.com/2010/04/05/why-vector-clocks-are-hard/ Thanks, Dan Daniel Reverri Developer Advocate Basho Technologies, Inc. [email protected] On Tue, Feb 15, 2011 at 10:11 AM, Les Mikesell <[email protected]>wrote: > Is riak suitable as a very reliable store where you have multiple feeds of > streaming data that are at least theoretically identical? That is, can you > count on writing multiple copies with the same keys at the same time to do > something reasonable regardless of cluster partitioning? And is this a > common usage scenario? > > -- > Les Mikesell > [email protected] > > _______________________________________________ > riak-users mailing list > [email protected] > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com >
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
