Re: match in order

2017-11-05 Thread Emir Arnautović
Hi Vincenco, Since it is about boosting, you might also take a look at edismax and pf2 and pf3 fields. It also supports slop (ps2 and ps3). HTH, Emir -- Monitoring - Log Management - Alerting - Anomaly Detection Solr & Elasticsearch Consulting Support Training - http://sematext.com/ > On 5 Nov

Re: match in order

2017-11-04 Thread Erick Erickson
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 only

Re: match in order

2017-11-04 Thread Vincenzo D'Amore
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 PM

Re: match in order

2017-11-04 Thread Erick Erickson
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 AM

match in order

2017-11-04 Thread Vincenzo D'Amore
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 t