Re: Edismax parsing when using pf parameter

2023-09-06 Thread Pierre Salagnac
I opened a pull request[1] that fixes the case reported. The issue was subqueries with grouped fields like "field:(term1 term2 term3), only the first term was skipped when generating the boost query with fields specified in pf parameter. Unfortunately, this pre-parsing (method splitIntoClauses())

Re: Edismax parsing when using pf parameter

2023-08-29 Thread Mónica Marrero
Thank you, Chris. Here is the JIRA ticket: https://issues.apache.org/jira/browse/SOLR-16953 Best, Mónica -- Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received th

Re: Edismax parsing when using pf parameter

2023-05-04 Thread Chris Hostetter
b\" | text:\"yyy zzz aaa bbb\"))", "parsedquery_toString":"+(+(+content:xxx +content:yyy +content:zzz) +(+(text:aaa) +(text:bbb))) (name:\"yyy zzz aaa bbb\" | text:\"yyy zzz aaa bbb\")", : Date: Thu, 4 May 2023 17:04:50 +0200 : Fr

Edismax parsing when using pf parameter

2023-05-04 Thread Mónica Marrero
Hi, I have found what I think is an inconsistent behaviour of the query parser when using the pf parameter. I am testing with the techproducts collection in Solr v9.2.1, defType=edismax, pf=text name a) Query= name:george AND (game AND thrones) Result= "parsedquery_toString":"+(+name:george +(+(