Hi, Thanks for the meetup in SF last week. I couldn't find the place for a long time and I was not able to hear everything that speakers said but it was good to see you. :)
I'm not sure if the following features confront with the architectural design and decisions of Riak but they would make many use cases easy/possible. Lists/Sets: Support for lists/sets on Riak like in Redis. The lists may even just store other keys instead of arbitrary values. That way you would be able to add/remove keys to a list/set with atomic operations. Twin Keys: Keys that refer to the same value. This way you can get the same document from different angles. For instance, one logic may refer to a value as a friend of a user, while another will refer friendships created today. Together with the further semantics you want to put to keys (this tokenizing key names and running logical operations on them) this will make it much more efficient to find a value without needing duplications etc. Best, Cagdas
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
