Correction: Sorry, I meant expiry_secs apples to a backend. All data in a given backend is subject to expiration--as defined in the backend configuration--by the merge process each time it runs.
________________________________ From: Nathan Wilken Sent: Friday, December 07, 2012 3:27 PM To: Ian Ha; riak-users@lists.basho.com Subject: RE: Does changing backend configs apply to existing data? The expiry_secs parameter applies to a bucket. This means all data in a given bucket is subject to expiration--as defined in the bucket configuration--by the merge process each time it runs. ________________________________ From: riak-users [riak-users-boun...@lists.basho.com] on behalf of Ian Ha [i...@blutrumpet.com] Sent: Friday, December 07, 2012 12:55 PM To: riak-users@lists.basho.com Subject: Does changing backend configs apply to existing data? Hi, We have a situation where our production riak cluster is missing config information. Specifically, we are running bitcask as our backend and we did not define an expiry_secs value, meaning data lives forever (which we don't want). Question: If we changed the config and define expiry_secs, does the expiry condition apply to all existing data or only to new data? Thanks in advance
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
