Re: X-Riak-Meta-* and Solr

Here's some more examples / writeups on indexing custom metadata fields, in addition to Zeeshan's links: https://github.com/basho/yokozuna/issues/5 https://github.com/basho/yokozuna/blob/develop/docs/TAGGING.md On Wed, Aug 12, 2015 at 12:25 AM, Zeeshan Lakhani wrote: > Hey Joe, > > Yes, you are

Re: X-Riak-Meta-* and Solr

Hey Joe, Yes, you are able to index with meta/tag fields. Here’s an example in one of our erlang tests using the riak_erlang pb client: https://github.com/basho/yokozuna/blob/32d71135644a579943799ff9a70b67dee0201f80/riak_test/yokozuna_essential.erl#L306

X-Riak-Meta-* and Solr

Is it possible to automatically index custom X-Riak-Meta-* fields with Solr? Do I have to create a custom extractor or modify the default search schema as outlined at http://docs.basho.com/riak/latest/dev/search/custom-extractors/ ? Here is my python code I am using to test: # Create search

Re: Rolling upgrade from 1.4.2 to 2.0.5

Hi Sujay, Yes, riak.conf is a riak 2 thing. If you're running 1.4, you would change the -setcookie in vm.args, exactly. And no, the node name doesn't have to match the cookie. The two are independent. On Tue, Aug 11, 2015 at 3:22 PM, Sujay Mansingh wrote: > Oh and also, does the first part of

Re: Rolling upgrade from 1.4.2 to 2.0.5

Oh and also, does the first part of the riak node name have to match the cookie? I.e. If I change the cookie to riaktest, does the node name have to be riaktest@{{ ip_addr }} ? On Tuesday, August 11, 2015, Sujay Mansingh wrote: > Thanks Dmitri > > When you say the cookie must be modified in /etc

Re: Rolling upgrade from 1.4.2 to 2.0.5

Thanks Dmitri When you say the cookie must be modified in /etc/riak/riak.conf, is that a riak 2 thing? I can see a -setcookie riak line in /etc/riak/vm.args, is that what you mean? Sujay ​ On Thu, Aug 6, 2015 at 2:11 PM, Dmitri Zagidulin wrote: > Sujay, > > You're right - the best way to verif

Re: why leaving riak cluster so slowly and how to accelerate the speed

1. About backuping new nodes of four and then using 'riak-admin force-replace'. what's the status of new added nodes? as you know, we want to replace one of leaving nodes. 2. what's the risk of 'riak-admin force-remove' 'riak@10.21.136.91' without backup? As you know, now the node(riak@10.21.136.9

Re: why leaving riak cluster so slowly and how to accelerate the speed

1. How to force leave "leaving"'s nodes without data loss? This depends on - did you back up the data directory of the 4 new nodes, before you reformatted them? If you backed them up (and then restored the data directory once you reformatted them), you can try: riak-admin force-replace 'riak@10.2

Re: Riak Search in bucket with write_once = true

Hey Zeeshan, Thanks for the clarification. I wasn't sure if it was a bug or intended behaviour, glad to hear it's the former and that it'll be fixed :-) best, Marius On 11 Aug 2015 3:43 am, "Zeeshan Lakhani" wrote: > Hey Marius, > > To put it simply, yes, 2.1.1 does not support write_once with