Ryan, I don't have any recommendations on how to compose your keys, just to note that if using bitcask they are stored in memory so you may have to watch out for that in regards to key length and # of objects.
What I really wanted to tell you is that secondary indices should arrive in some form in the near future. Using composite keys with key filtering should be able to fill in for the time being. Another option is to use Search and enable indexing on your buckets. -Ryan On Wed, Jun 1, 2011 at 9:19 PM, Ryan Caught <[email protected]> wrote: > Hi everyone, > I have some questions regarding key composition and secondary indexes. > > Key filters seem really useful, and because of this, I find myself > designing keys that have (perhaps) too many elements within them. > > - Are there any best practices concerning key composition? > - Does the composition of a key in a bitcask setup influence speed? (It > seems to in > Innodb<http://lists.basho.com/pipermail/riak-users_lists.basho.com/2011-April/003819.html> > ) > - Is there a maximum key length? > > Lastly, do integrated secondary indexes exist in Riak yet? This link > suggests they are > coming<http://www.oscon.com/oscon2011/public/schedule/detail/19806> but > I've been unable to find any other evidence of their arrival. > > Thanks! > Ryan > > _______________________________________________ > 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
