Re: Concurrency hazard when updating links

I've written this little link index kit that can be used to manage external "link objects" https://github.com/krestenkrab/riak_link_index Which uses vectorclocks on individual links (they are contained in a riak_link_set) so link updates are done

Re: Concurrency hazard when updating links

How is this handled on requests where the the server does the link insertion and walking for you? That is, you have some existing links and simultaneously add multiple new items that add themselves to the same links, then ask the server to return the values from link walking. Does the client

Re: Concurrency hazard when updating links

And here's the link I neatly forgot to include: http://wiki.basho.com/Vector-Clocks.html Mathias Meyer Developer Advocate, Basho Technologies On Mittwoch, 22. Juni 2011 at 17:18, Mathias Meyer wrote: > Manuel, > > what you're seeing is not specific to links, it's generally how concurrent > u

Re: Concurrency hazard when updating links

Manuel, what you're seeing is not specific to links, it's generally how concurrent updates to a single object are handled in Riak, links are no exception. If you want to handle that properly you need to enable the allow_mult property on the bucket in question. Now, whenever two clients update

Concurrency hazard when updating links

Hello, Probably I have some miss understating on whats the best way to update links in Riak, but I am wondering if you know about this hazard when updating links: client A: getLinks(X) client B: getLinks(X) clientB:updateLinks(X) clientA:updateLinks(X) where the update made by B is cleaned by