Re: Invalid parsing with solr edismax operators

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 < > https://issues.apache.

Re: Invalid parsing with solr edismax operators

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 for this as a bug since > eit

Re: Invalid parsing with solr edismax operators

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 add the mm=2 > when searchi

Re: Invalid parsing with solr edismax operators

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 w

Re: Invalid parsing with solr edismax operators

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 >TotalField >

Re: Invalid parsing with solr edismax operators

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 Mahmoud, > can you send us the

Re: Invalid parsing with solr edismax operators

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

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, > > I'm using solr 4.8.1

Invalid parsing with solr edismax operators

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", "start

Invalid parsing with solr edismax operators

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", "start":"

Re: edismax operators

> solr version 4.8.1 > > Thanks, > Mahmoud > > On Thu, Apr 2, 2015 at 6:56 PM, Davis, Daniel (NIH/NLM) [C] < > daniel.da...@nih.gov> wrote: > > > Thanks Shawn, > > > > This is what I thought, but Solr often has features I don't anticipate. >

Re: edismax operators

, 2015 at 6:56 PM, Davis, Daniel (NIH/NLM) [C] < daniel.da...@nih.gov> wrote: > Thanks Shawn, > > This is what I thought, but Solr often has features I don't anticipate. > > -Original Message- > From: Shawn Heisey [mailto:apa...@elyograg.org] > Sent: Thursday, April

RE: edismax operators

Thanks Shawn, This is what I thought, but Solr often has features I don't anticipate. -Original Message- From: Shawn Heisey [mailto:apa...@elyograg.org] Sent: Thursday, April 02, 2015 12:54 PM To: solr-user@lucene.apache.org Subject: Re: edismax operators On 4/2/2015 9:59 AM,

Re: edismax operators

On 4/2/2015 9:59 AM, Davis, Daniel (NIH/NLM) [C] wrote: > Can the mm parameter be set per clause?I guess I've ignored it in the > past aside from setting it once to what seemed like a reasonable value. > That is probably replicated across every collection, which cannot be ideal > for relevanc

Re: edismax operators

> From: Shawn Heisey [mailto:apa...@elyograg.org] > Sent: Thursday, April 02, 2015 11:13 AM > To: solr-user@lucene.apache.org > Subject: Re: edismax operators > > On 4/2/2015 8:35 AM, Mahmoud Almokadem wrote: >> Thank you Jack for your clarifications. I used regular defType an

RE: edismax operators

o:apa...@elyograg.org] Sent: Thursday, April 02, 2015 11:13 AM To: solr-user@lucene.apache.org Subject: Re: edismax operators On 4/2/2015 8:35 AM, Mahmoud Almokadem wrote: > Thank you Jack for your clarifications. I used regular defType and set > q.op=AND so all terms without operators are mu

Re: edismax operators

On 4/2/2015 8:35 AM, Mahmoud Almokadem wrote: > Thank you Jack for your clarifications. I used regular defType and set > q.op=AND so all terms without operators are must. How can I use this with > edismax? The edismax parser is capable of much more granularity than simply AND/OR on the default ope

Re: edismax operators

Thank you Jack for your clarifications. I used regular defType and set q.op=AND so all terms without operators are must. How can I use this with edismax? Thanks, Mahmoud On Thu, Apr 2, 2015 at 2:14 PM, Jack Krupansky wrote: > The parentheses signal a nested query. Your plus operator applies to

Re: edismax operators

The parentheses signal a nested query. Your plus operator applies to the overall nested query - that the nested query must match something. Use the plus operator on each of the discrete terms if each of them is mandatory. The plus and minus operators apply to the overall nested query - they do not

edismax operators

Hello, I've a strange behaviour on using edismax with multiwords. When using passing q=+(word1 word2) I got "rawquerystring": "+(word1 word2)", "querystring": "+(word1 word2)", " parsedquery": "(+(+(DisjunctionMaxQuery((title:word1)) DisjunctionMaxQuery((title:word2)/no_coord", "parsedquery_t