Jeroen, You can run multiple bitcask backends using the multi_backend, and configure them differently (one with a timeout and one without). That's what we do when we need this. The only issue is that you need to watch the number of file descriptors, since even one bitcask is pretty fd-hungry :-)
Kresten Mobile: + 45 2343 4626 | Skype: krestenkrabthorup | Twitter: @drkrab Trifork A/S | Margrethepladsen 4 | DK- 8000 Aarhus C | Phone : +45 8732 8787 | www.trifork.com<http://www.trifork.com/> On Nov 29, 2011, at 10:37 AM, Jeroen van Dijk wrote: Hi all, I'm currently investigating of how to structure my data in Riak. I'm thinking of having buckets that have the purpose of storing the raw data and having buckets that store certain views on this data to minimize lookups and mapreduce operations at runtime. So the latter would in effect be a cache store of these views. I saw http://wiki.basho.com/Bitcask.html#Automatic-Expiration and I would conclude that I could use bitcask storage to achieve this. I'm currently just wondering whether the expiry_secs setting is a global one. Is it possible to set this expiry per bucket? Otherwise I would have to give up the use of Bitcask for other scenarios than caching I assume. Cheers, Jeroen _______________________________________________ riak-users mailing list [email protected]<mailto:[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
