That’s not really an option, I think. Our buckets are named “<prefix>-YYYY-MM” and the keys are user login names. Re-using the date-based buckets wouldn’t make much sense in our case.
> On Jun 3, 2015, at 2:48 PM, Igor Birman <igor_bir...@yahoo.com> wrote: > > Can you recycle the keys rather than deleting them? We mark them as > available for deletion and keep a key recycle pool where we pull new keys > from. > > > On Wednesday, June 3, 2015 12:37 PM, Peter Herndon <tphern...@gmail.com> > wrote: > > > Hi list, > > We’re looking for the best way to handle large scale expiration of > no-longer-useful data stored in Riak. We asked a while back, and the > recommendation was to store the data in time-segmented buckets (bucket per > day or per month), query on the current buckets, and use the streaming list > keys API to handle slowly deleting the buckets that have aged out. > > Is that still the best approach for doing this kind of task? Or is there a > better approach? > > Thanks! > > —Peter Herndon > Sr. Application Engineer > @Bitly > _______________________________________________ > riak-users mailing list > riak-users@lists.basho.com > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > > _______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
