> you'll need to look in etc/app.config in the release directory and change the value for the storage_backend setting to riak_kv_index_backend
Thanks. How stable is the riak_kv_index_backend? If we're aiming to go to prod in a couple months would we be better advised to use riak search? It seems as though it's functionality is a superset of secondary indexing, though more painful to implement. --Craig On Wed, Aug 3, 2011 at 9:48 PM, Jeremiah Peschka <jeremiah.pesc...@gmail.com > wrote: > I believe 1.0 is scheduled for November. > > --- > Jeremiah Peschka > Founder, Brent Ozar PLF, LLC > > On Aug 3, 2011, at 9:47 PM, Antonio Rohman Fernandez wrote: > > > Another question... the old problem of querying smaller buckets with > MapReduce is resolved with secondary indexes? > > following this pattern => curl > http://127.0.0.1:8098/buckets/loot/index/category_bin/eq/armor i think > Riak doesn't have to check all the buckets/keys in memory to match the one > you look for as it happened on a MapReduce, right? so > http://127.0.0.1:8098/buckets/rohman_messages/index/date_int/eq/20110801would > give me all messages from Rohman ( in a personalized bucket ) for the > day 1st of August of 2011 in a much faster way, right? > > thanks > > > > Rohman > > > > On Thu, 04 Aug 2011 12:38:17 +0800, Antonio Rohman Fernandez wrote: > > > >> seeing OSCON's PDF... when will we be able to have Riak 1.0 with > secondary indexes out? This is an improvement that can help me pretty well > out on my project. Any ETA? > >> thanks > >> > >> Rohman > >> > >> On Wed, 3 Aug 2011 22:02:53 -0600, Kelly McLaughlin wrote: > >> > >> Craig, > >> The default backend is bit cask and if you want to use the indexes > you'll need to look in etc/app.config in the release directory and change > the value for the storage_backend setting to riak_kv_index_backend instead > of riak_kv_bitcask_backend. I suspect that's the problem. Cheers. > >> Kelly > >> > >> On Aug 3, 2011, at 9:42 PM, Craig Muth wrote: > >> > >> I'm running the code example from > http://rusty.basho.com.s3.amazonaws.com/Presentations/2011-OSCONData-Portland.pdf > >> This succeeds: > >> curl \ > >> -X PUT \ > >> -d "OPAQUE_VALUE" \ > >> -H "x-riak-index-category_bin: armor" \ > >> -H "x-riak-index-price_int: 400" \ > >> http://127.0.0.1:8098/buckets/loot/keys/gauntlet24 > >> This verifies it's getting there: > >> curl http://127.0.0.1:8098/riak/loot/gauntlet24 > >> => OPAQUE_VALUE > >> However, this finds nothing: > >> curl http://127.0.0.1:8098/buckets/loot/index/category_bin/eq/armor > >> => {"keys":[]} > >> Whereas in the presentation it says it should return > {"keys":["gauntlet24"]} > >> Any ideas? Just grabbed the latest from github master. > >> --Craig > >> _______________________________________________ > >> riak-users mailing list > >> riak-users@lists.basho.com > >> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > >> -- > >> <blocked.gif> > >> <blocked.gif> Antonio Rohman Fernandez > >> CEO, Founder & Lead Engineer > >> roh...@mahalostudio.com Projects > >> MaruBatsu.es > >> PupCloud.com > >> Wedding Album<blocked.gif> > > -- > > > > Antonio Rohman Fernandez > > CEO, Founder & Lead Engineer > > roh...@mahalostudio.com Projects > > MaruBatsu.es > > PupCloud.com > > Wedding Album > > _______________________________________________ > > riak-users mailing list > > riak-users@lists.basho.com > > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > > > _______________________________________________ > riak-users mailing list > riak-users@lists.basho.com > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com >
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
