On 7 February 2015 at 06:21, Kota Uenishi wrote:
> Bitcask doesn't have such interface like hooking anything. As of
> internal data structure of Riak CS built on top of Riak, bitcask keys
> don't correspond simply to leveldb key. Say, things like this cannot
> happen: "all tombstones of blocks of
Bitcask doesn't have such interface like hooking anything. As of
internal data structure of Riak CS built on top of Riak, bitcask keys
don't correspond simply to leveldb key. Say, things like this cannot
happen: "all tombstones of blocks of this object were collected and
space were reclaimed by mer
Hi,
As far as I understand, Riak CS uses bitcask for data storage and
leveldb for metadata.
Trying to implement expiration of data in riak cs, bitcask expiration
works fine, but of course metadata are still in the leveldb backend. Is
there any way to expire metadata from riak cs automatically ?
