If you use some hash function of the "post" attribute as the key of the object, then even if the key is written multiple times, there will be no duplicate (because the content maps directly to the key, this is also called "content-addressable"). If you need some other key-scheme, external synchronization and perhaps indexing is needed, especially if the window of time when duplicates will be created is small.
On Wed, Dec 26, 2012 at 11:50 AM, idmartin <[email protected]> wrote: > Im thinking about switching a project to riak. Whats the best way to deal > with duplicate strings in riak. > > I will have a bucket of obj's with one being a "post" like attribute ( > small-med-large string ). What the best way of avoiding adding duplicates > into the bucket based on this key? > > > > -- > View this message in context: > http://riak-users.197444.n3.nabble.com/dealing-with-duplicate-values-in-riak-tp4026416.html > Sent from the Riak Users mailing list archive at Nabble.com. > > _______________________________________________ > riak-users mailing list > [email protected] > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com -- Sean Cribbs <[email protected]> Software Engineer Basho Technologies, Inc. http://basho.com/ _______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
