Re: match in order

This _particular_ use case might be a good candidate for shingles. That filter pairs up tuples into tokens, so your docs would have A_B A_C A_C B_D and the search would be broken up (assuming the appropriate parameters to ShingleFilterFacotry) to X_A A_B B_Y thus would match the specified doc

recent utf8 problems

Hi, We recently discovered issues with solr with converting utf8 code in the search. One or two month ago everything was still working. - What might have caused it is a Java update (Java 8 Update 151). - We are using firefox as well as chrome for displaying results. - We tested it with Solr

Re: match in order

Thanks Erick. Right, if there is no slop specified it is like have an "exact match". So I can simplify the query in: bq=field1:("X A" OR "A B" OR "B Y")^10 I'm struggling to understand if there is any way to split the user query in pairs directly with solr. > On Sat, Nov 4, 2017 at 6:32

Leader initiated recovery authentication failure

Hi All, After enabling basic authentication for solr cloud, I noticed that the internal leader initiated recovery failed with 401 response. The recovery request from leader: GET //replica1.mycloud.com:9090/solr/admin/cores?action=*REQUESTRECOVERY*=replica1=javabin=2 HTTP/1.1" 401 310 "-"

Re: match in order

Looks good to me. The only thing I'd mention is that in the example given, complexprhase query is unnecessary, but only because there's no "slop" specified. If by "near" you can also mean "within 3 words" or some such, then you need complexPhraseQuery.. FWIW, Erick On Sat, Nov 4, 2017 at 10:12

match in order

Hi, I have a field field1 where there are only pairs of terms, for example the documents doc1 { field1 : "A B", title : "Hello title 1" } doc2 { field1 : "A C", title : "Hello title 2" } doc3 { field1 : "A D", title : "Hello title 3" } doc4 { field1 : "B D", title : "Hello title 4" } I have

Re: Advice on Stemming in Solr

Hi Emir, We are looking at the configuration, to try to adjust the rules to suit our use case. Regards, Edwin On 3 November 2017 at 16:24, Emir Arnautović wrote: > Hi Edwin, > Hunspell is configurable, language independent library and you can define > any

Re: SolrClould 6.6 stability challenges

not committing after the batch. made sure we have that turned off. maxTime is set to 30 (300 seconds), openSearcher is set to true. On Sat, Nov 4, 2017 at 6:50 PM, Amrit Sarkar wrote: > Pretty much what Emir has stated. I want to know, when you saw; > > all of this

Re: SolrClould 6.6 stability challenges

Pretty much what Emir has stated. I want to know, when you saw; all of this runs perfectly ok when indexing isn't happening. as soon as > we start "nrt" indexing one of the follower nodes goes down within 10 to 20 > minutes. When you say "NRT" indexing, what is the commit strategy in indexing.

Re: SolrClould 6.6 stability challenges

Hi Rick, Do you see any errors in logs? Do you have any monitoring tool? Maybe you can check heap and GC metrics around time when incident happened. It is not large heap but some major GC could cause pause large enough to trigger some snowball and end up with node in recovery state. What is