Re: Find part of long query in shorter fields

2016-07-21 Thread CA
Hi Ahmet! Thank you for that information. I was wondering whether dismax is kind of „deprecated“ or - if not - when would I use dismax in preference to edismax. The documentation sounds to me like „edismax is dismax+ : is does everything dismax does, and more“. Chantal Am 21.07.2016 um 14:43 s

Re: Find part of long query in shorter fields

2016-07-21 Thread Ahmet Arslan
Hi, If you want to disable operators altogether please use dismax instead of edismax. In dismax, only + and - unary operators are supported, if i am not wrong. I don't remember the situation of quotations for the phrase query. Ahmet On Tuesday, July 19, 2016 8:29 PM, CA wrote: Just for the r

Re: Find part of long query in shorter fields

2016-07-19 Thread CA
Just for the records: After realizing that with „defType=dismax“ I really do get the expected output I’ve found out what I need to change in my edismax configuration: false Then this will work: > q=Braun Series 9 9095CC Men's Electric Shaver Wet/Dry with Clean and Renew > Charger > // edismax

Re: Find part of long query in shorter fields

2016-07-18 Thread CA
Hi Ahmet, thank you for the link. It helped me to find more resources. What I still don’t understand, though, is why the edismax returns one of the documents with a partial hit and not the other: q=Braun Series 9 9095CC Men's Electric Shaver Wet/Dry with Clean and Renew Charger // edismax wi

Re: Find part of long query in shorter fields

2016-07-16 Thread Ahmet Arslan
Hi Chantal, Please see https://issues.apache.org/jira/browse/LUCENE-7148 ahmet On Saturday, July 16, 2016 3:48 PM, CA wrote: Hello all, our index contains product offers from online shops. The fields we are indexing have all rather short values: the name of the product, the brand, the pric