Re: Invalid parsing with solr edismax operators

2015-11-05 Thread Mahmoud Almokadem
Thanks Jack. I have reported it as a bug on JIRA https://issues.apache.org/jira/browse/SOLR-8237 Mahmoud > On Nov 4, 2015, at 5:30 PM, Jack Krupansky wrote: > > I think you should go ahead and file a Jira ticket

Re: Invalid parsing with solr edismax operators

2015-11-05 Thread Jack Krupansky
Great. Now, we'll have to see if any enterprising committers will step up and take a look. -- Jack Krupansky On Thu, Nov 5, 2015 at 4:46 AM, Mahmoud Almokadem wrote: > Thanks Jack. I have reported it as a bug on JIRA > > https://issues.apache.org/jira/browse/SOLR-8237 <

Re: Invalid parsing with solr edismax operators

2015-11-04 Thread Alessandro Benedetti
Here we go : Title^200 TotalField^1 + Jack explanation and you have the parsed query explained ! Cheers On 4 November 2015 at 12:56, Mahmoud Almokadem wrote: > Thank you Alessandro for your reply. > > Here is the request handler > > > > > explicit >10 >

Re: Invalid parsing with solr edismax operators

2015-11-04 Thread Alessandro Benedetti
Hi Mahmoud, can you send us the solrconfig.xml snippet of your request handler please ? It's kinda strange you get a boost factor for the Title field and that parsing query, according to your config. Cheers On 4 November 2015 at 08:39, Mahmoud Almokadem wrote: > Hello,

Re: Invalid parsing with solr edismax operators

2015-11-04 Thread Mahmoud Almokadem
Thank you Alessandro for your reply. Here is the request handler explicit 10 TotalField AND edismax Title^200 TotalField^1 Mahmoud > On Nov 4, 2015, at 2:43 PM, Alessandro Benedetti > wrote: > > Hi

Re: Invalid parsing with solr edismax operators

2015-11-04 Thread Jack Krupansky
It is debatable whether this is a bug or just a poorly documented interaction of q.op, mm, and nested queries (within parentheses.) Personally, I'd say it is a bug. Edismax is only obeying q.op and mm for the top-level of the query - once you nest within parentheses the default operator reverts to

Re: Invalid parsing with solr edismax operators

2015-11-04 Thread Mahmoud Almokadem
I removed the q.op=“AND” and add the mm=2 when searching for (public libraries) I got 19 with "parsedquery_toString": "+(((Title:public^200.0 | TotalField:public^0.1) (Title:libraries^200.0 | TotalField:libraries^0.1))~2)", and when adding + and searching for +(public libraries) I got 1189

Re: Invalid parsing with solr edismax operators

2015-11-04 Thread Jack Krupansky
I think you should go ahead and file a Jira ticket for this as a bug since either it is an actual bug or some behavior nuance that needs to be documented better. -- Jack Krupansky On Wed, Nov 4, 2015 at 8:24 AM, Mahmoud Almokadem wrote: > I removed the q.op=“AND” and

Invalid parsing with solr edismax operators

2015-11-04 Thread Mahmoud Almokadem
Hello, I'm using solr 4.8.1. Using edismax as the parser we got the undesirable parsed queries and results. The following is two different cases with strange behavior: Searching with these parameters "mm":"2", "df":"TotalField", "debug":"true", "indent":"true", "fl":"Title",

Invalid parsing with solr edismax operators

2015-11-01 Thread Mahmoud Almokadem
Hello, I'm using solr 4.8.1. Using edismax as the parser we got the undesirable parsed queries and results. The following is two different cases with strange behavior: Searching with these parameters "mm":"2", "df":"TotalField", "debug":"true", "indent":"true", "fl":"Title",