On Wed, Feb 23, 2011 at 10:40 AM, Les Mikesell <lesmikes...@gmail.com>wrote: > > > > Thanks! A couple more somewhat related questions: is that atomic update > nature hard to duplicate outside of luwak (say by a client that needs to > keep several items in sync), and if the luwak blocks are immutable, how do > you ever clean up the space used by data that has been deleted or modified > and no longer referenced? > > For your first question, I believe the onus to make multiple object updates atomic is on you, the application developer. One of the, perhaps easier, ways to achieve this would be to wrap all the data in one object?
Second, you don't; not at this time at least. Luwak allows you to delete the file reference, but not the data itself. It's the very nature of the fact that it's an immutable, persistent data structure that makes this so. If two files share a block, then you can't simply delete the blocks under a file, but instead must perform something more like garbage collection. If you're up for it, I have some proof of concept code on my fork of Luwak. I got GC to work, to an extent. IIRC, once I got past 10-15GB things started to degrade quickly. When I get more time I plan to return to it. https://github.com/rzezeski/luwak -Ryan
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
