Re: After Solr 5.5, mm parameter doesn't work properly

2016-06-02 Thread Greg Pendlebury
I think the confusion stems from the legacy implementation partially conflating q.op with mm for users, when they are very different things. q.op tells Solr how to insert boolean operators before they are converted into occurs flags, and then downstream, mm applies on _only_ the SHOULD occurs

Re: After Solr 5.5, mm parameter doesn't work properly

2016-06-02 Thread Jan Høydahl
[Aside] Your quote style is confusing, leaving my lines unquoted and your new lines quoted?? [/Aside] > So in relation to the OP's sample queries I was pointing out that 'q.op=OR > + mm=2' and 'q,op=AND + mm=2' are treated as identical queries by Solr 5.4, > but 5.5+ will manipulate the occurs

Re: After Solr 5.5, mm parameter doesn't work properly

2016-06-01 Thread Greg Pendlebury
I would describe that subtly differently, and I think it is where the difference lies: "Then from 4.x it did not care about q.op if mm was set explicitly" >> I agree. q.op was not actually used in the query, but rather as a way of inferred the default mm value. eDismax still ignored whatever q.op

Re: After Solr 5.5, mm parameter doesn't work properly

2016-06-01 Thread Jan Høydahl
Edismax used to default to mm=100% and not care about q.op at all Then from 4.x it did not care about q.op if mm was set explicitly, but if mm was not set, then q.op=OR —> mm=0%, q.op=AND —> mm=100% And from 5.5 it seems as q.op does something even if mm is set... -- Jan Høydahl, search

Re: After Solr 5.5, mm parameter doesn't work properly

2016-06-01 Thread Greg Pendlebury
But isn't that the default value? In this case the OP is setting mm explicitly to 2. Will have to look at those code links more thoroughly at work this morning. Apologies if I am wrong. Ta, Greg On Wednesday, 1 June 2016, Jan Høydahl wrote: > > 1. jun. 2016 kl. 03.47

Re: After Solr 5.5, mm parameter doesn't work properly

2016-06-01 Thread Jan Høydahl
> 1. jun. 2016 kl. 03.47 skrev Greg Pendlebury : > I don't think it is 8812. q.op was completely ignored by edismax prior to > 5.5, so it is not mm that changed. That is not the case. Prior to 5.5, mm would be automatically set to 100% if q.op==AND See

Re: After Solr 5.5, mm parameter doesn't work properly

2016-05-31 Thread Greg Pendlebury
I don't think it is 8812. q.op was completely ignored by edismax prior to 5.5, so it is not mm that changed. If you do the same 5.4 query with q.op=OR I suspect it will not change the debug query at all. On 30 May 2016 at 21:07, Jan Høydahl wrote: > Hi, > > This may be

Re: After Solr 5.5, mm parameter doesn't work properly

2016-05-30 Thread Jan Høydahl
Hi, This may be related to SOLR-8812, but still different. Please file a JIRA issue for this. -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com > 29. mai 2016 kl. 18.20 skrev Issei Nishigata : > > Hi, > > “mm" parameter does not work properly,

After Solr 5.5, mm parameter doesn't work properly

2016-05-29 Thread Issei Nishigata
Hi, “mm" parameter does not work properly, when I set "q.op=AND” after Solr 5.5. In Solr 5.4, mm parameter works expectedly with the following setting. --- [schema]         [request] http://localhost:8983/solr/collection1/select?defType=edismax=AND=2=solar — After Solr 5.5, the result