Re: Secondary Index Query across multiple buckets

2011-12-15 Thread Rusty Klophaus
Hi Jeremy, Yes, in this scenario, a single query under a large bucket will be faster, for all of the reasons that you mentioned... connection setup/teardown, query processing overhead, and seeking to/reading index information from disk. Best, Rusty On Thu, Dec 15, 2011 at 11:07 AM, Jeremy Raymon

Re: Secondary Index Query across multiple buckets

2011-12-15 Thread Jeremy Raymond
Thanks Rusty. What would perform better, running multiple queries across several buckets or a single query under one large one? I'd guess the later because of whatever overhead is involved in setting up the connection to Riak and whatever Riak does to setup and run a mapred/index query. -- Jeremy

Re: Secondary Index Query across multiple buckets

2011-12-15 Thread Rusty Klophaus
Hi Jeremy, Currently, Secondary Indexes are scoped per bucket. There is no good way to run a Secondary Index query across multiple buckets, short of running multiple queries. You are correct in that you could store the items in a single bucket provided that they all have unique keys. In the Level

Re: Secondary Index Query across multiple buckets

2011-12-15 Thread Jeremy Raymond
Let me pose the question a different way. What is a good way to pull out objects across multiple buckets based upon some secondary data that is not their key? The items in the buckets all have unique keys. Maybe move them all into a single bucket (millions of items) and then I could use secondary