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
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
Is an intermediate upgrade recommended? 0.14.2 --> 1.0/1.1 --> 1.2?
From: riak-users-boun...@lists.basho.com [riak-users-boun...@lists.basho.com]
on behalf of Sean Cribbs [s...@basho.com]
Sent: Wednesday, August 08, 2012 6:35 AM
To: Sebastian Cohnen
Cc: riak-us
Can you send a list of the *.data files and their sizes?
From: riak-users-boun...@lists.basho.com [riak-users-boun...@lists.basho.com]
On Behalf Of raghwani sohil [sohil4...@gmail.com]
Sent: Thursday, August 25, 2011 11:07 PM
To: Aphyr
Cc: riak-users@lists.basho.
How about this?
#!/bin/sh
...
for i in data/expiring_bitcask/* ; do $ERTS_PATH/to_erl $PIPE_DIR>, riak_kv_bitcask_backend, [
{expiry_secs, 86400},
{max_file_size, 134217728},
