>> Could you give me an example of a use case for reproducing case 1 in a unit >> test? Case 2a is easy but I've tried several ways to reliably produce case 1 >> and I'm not getting anywhere. > > A tombstone will exist for 3s by default. With the Java client I can > reproduce it every time with:
Ah, of course at that time I didn't know about the magic combination of a 404 plus a vclock header so my client cannot currently reproduce this. >> My Scala client basically just treats tombstones like completely deleted >> values, so for case 1 that would lead to "normal" 404 behavior and during >> conflict resolution it will just ignore/skip tombstones. But if lots of >> people are interested in dealing with tombstones directly I might have to >> change that to something similar to what you did in the java client. > > Yeah ... it's a hard road trying to guess how people are going to want > to use something. Personally? Since the feature exists I'd support it > if only for the sake of completeness. Any idea whether there are other clients (like for Ruby, Python, Erlang, etc.) that expose this? >> Are there any plans on adding a documentation section about tombstones and >> deletes in Riak? I think that would definitely be helpful for other people >> writing clients. > > I'll raise that issue this week; there probably should be. In the mean > time probably the most comprehensive information on the subject can be > found here: > http://lists.basho.com/pipermail/riak-users_lists.basho.com/2011-October/006048.html I think it is important to document this if you want to promote the community writing clients for languages that you can't or won't support. It's the only source of information we have. Thanks, Age _______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
