On 16/07/13 07:16, Gabriel Littman wrote:
Another posibility is to create a new bucket for each test run.
+1
I think using a unique bucket name is definitely the only sane way to go.
It also prevents you from having weird issues if you run two tests
simultaneously (as can easily happen once you have multiple developers
and automated integration testing).
On Mon, Jul 15, 2013 at 12:06 PM, Matthew Dawson <matt...@mjdsystems.ca
<mailto:matt...@mjdsystems.ca>> wrote:
Hi Seth,
On July 14, 2013 02:25:02 PM Seth Bunce wrote:
> I had a similar problem. I mitigated the problem by appending a
> current timestamp (in nanoseconds) to the keys I'm using in my tests.
> This way I don't have to worry about waiting for Riak to reap
> tombstones after 3 seconds and I don't have to use
> delete_mode=immediate. I still do a list keys + delete before each
> test.
I think this is what I'm going to have to do. I tried all the different
delete_mode settings, but none of them seemed to help. Thanks for the
suggestion!
_______________________________________________
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
