Thank you. I am creating indexes with:
curl -i -XPUT http://192.168.1.10:8098/yz/index/allLogs \ -H 'content-type: application/json' \ -d '{"schema" : "_yz_default", "bucket" : "logs" }' But when I check the index with: curl -i http://192.168.1.10:8098/yz/index/allLogs It drops the bucket association HTTP/1.1 200 OK Server: MochiWeb/1.1 WebMachine/1.10.5 (jokes are better explained) Date: Wed, 20 Nov 2013 20:45:21 GMT Content-Type: application/json Content-Length: 41 {"name":"allLogs","schema":"_yz_default"} Also what is going on here curl -XPUT -H'content-type:application/json' http://localhost:8098/buckets/people/keys/me \ -d'{ "name_s" : "kartik" }' Why not: curl -XPUT -H'content-type:application/json' http://localhost:8098/rial/people/me<http://localhost:8098/buckets/people/keys/me> \ -d'{ "name_s" : "kartik" }' On Tue, Nov 19, 2013 at 5:32 PM, Eric Redmond <eredm...@basho.com> wrote: > Kartik, > > Your confusion is understandable, since our docs are not up to date yet > (and they won't be until closer to the final 2.0 release date). Because of > this, the docs you're reading correspond to the old version of RiakSearch, > and not the new Search (codenamed yokozuna). Thus, you cannot rely on the > docs just yet. > > The good news is, we do have some docs for yokozuna on github: > > https://github.com/basho/yokozuna/tree/develop/docs > > You do have yokozuna enabled by setting `yokozuna = on`. Don't worry about > those links going to 404, because they aren't relevant at this time. > > You do not need to add postcommit hooks. In 2.0.0pre5 you merely need to > create an index, then associate that index with a bucket (you can > optionally create a custom solr schema and use that for the index, or you > can simply use the default schema): > > https://github.com/basho/yokozuna/blob/develop/docs/ADMIN.md#index-creation > > (note that this will change in the 2.0.0 final release, but it sufficient > to get started in pre5). > > After you've created an index and associated it with a bucket, then you > need only insert json, xml, or plain text, which will be extracted based on > the field. If you suffix your json or xml field named with a dynamic field > parameter, it will be indexed as that type (the list can be found here > https://github.com/basho/yokozuna/blob/develop/priv/default_schema.xml). > > eg, assuming the bucket "people" has an index associated with the same > name: > > # Add a JSON value: > curl -XPUT -H'content-type:application/json' > http://localhost:8098/buckets/people/keys/me \ > -d'{ "name_s" : "kartik" }' > > # perform a search > curl "http://localhost:8098/search/people?q=name_s:kar*"; > > Hope that helps. We'll updating the docs in the next month. > > Eric > > On Nov 19, 2013, at 7:28 AM, Kartik Thakore <thakore.kar...@gmail.com> > wrote: > > Hello, > > I am reviewing Riak 2.0pre5 for use and I am confused with the search > documentation provided here: > > http://docs.basho.com/riak/2.0.0pre5/dev/using/search/ > > It tells me to enable search: > > http://docs.basho.com/riak/2.0.0pre5/ops/advanced/configs/search/ > > But there is no such file in etc anymore after I use make rel to build > Riak 2.0 > > So I enabled yokozuna = on and I think I have it enabled > > [RIAK MACHINE]:8098 is showing: > > yz_wm_extract > yz_wm_index > yz_wm_schema > yz_wm_search > yz_wm_search > yz_wm_search > > But these links go to 404 pages > > Now how do I set up search on a bucket? Do I still need to do post commit > hooks on the buckets? > > Thank You for your help > > > _______________________________________________ > 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
