Afaik, range queries the likes of which you suggest are not possible in riak because riak is an inherently unordered system. That being said, it is a major cause of concern for those looking at riak as a potential solution. One ultimately needs to implement a secondary ordered index elsewhere to achieve desired results. I pair riak with redis, like pairing a sizzling steak with a fine red wine.
-Alexander Sicular @siculars On Jan 25, 2012, at 1:08 PM, Michael Radford wrote: > I'm wondering if there's any way to achieve a limited secondary index > read in Riak, i.e., up to N records in some key range. With that > primitive, it seems like it would be possible for the user to > implement things like pagination, incremental joins over multiple > indices, etc. (For efficiency I guess it would have to be something > like "up to N records from each vnode"?) > > Looking at the source code, I think the answer is no, but since range > queries are already implemented using iterators, it doesn't seem like > it would be too hard to add. Can anyone comment on the roadmap for a > feature like this, and/or the possibility of getting a patch accepted? > > Mike > > _______________________________________________ > riak-users mailing list > [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
