This is what we do for CorrugatedIron integration testing. Test buckets typically have a test name + UUID. Which makes it interesting when I try to verify data via curl while I'm debugging. But it also keeps me from polluting my testing buckets with the output of other failed tests.
--- Jeremiah Peschka - Founder, Brent Ozar Unlimited MCITP: SQL Server 2008, MVP Cloudera Certified Developer for Apache Hadoop On Mon, Jul 15, 2013 at 2:16 PM, Gabriel Littman <[email protected]> wrote: > Hi, > > Another posibility is to create a new bucket for each test run. > > Gabe > > On Mon, Jul 15, 2013 at 12:06 PM, Matthew Dawson <[email protected]>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! >> -- >> Matthew >> _______________________________________________ >> 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 > >
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
