[jira] [Commented] (SOLR-9174) After Solr 5.5, mm parameter doesn't work properly
[
https://issues.apache.org/jira/browse/SOLR-9174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324579#comment-15324579
]
Steve Rowe commented on SOLR-9174:
--
bq. So if a user uses explicit operators, then I think "mm" should be ignored.
This was the case < 5.5.0 and it appears you restored that today for 6.1.
No, I didn't - the SOLR-8812 changes were all about choosing a more appropriate
mm default where there is no explicit mm spec.
bq. A better example may have been a "ipod AND power AND nonexistentword" which
should return nothing despite the 'mm'.
Two issues with the above example:
1. "AND" is ignored when deciding whether a query has operators that should
affect mm. AFAICT this behavior is as old as edismax. I don't understand why
it's this way, since all other boolean operators are respected, especially
since the "+" operator has always been among those that cause default mm to be
0%. I didn't change this in my SOLR-8812 commit.
2. A query with all required clauses will be unaffected by mm (which applies to
optional clauses), regardless of whether the explicit mm spec is ignored.
> After Solr 5.5, mm parameter doesn't work properly
> --
>
> Key: SOLR-9174
> URL: https://issues.apache.org/jira/browse/SOLR-9174
> Project: Solr
> Issue Type: Bug
> Components: query parsers, search
>Affects Versions: 5.5, 6.0, 6.0.1
>Reporter: Issei Nishigata
>
> “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]
> {code:xml}
>
>
> maxGramSize="2"/>
>
>
> {code}
> [request]
> {quote}
> http://localhost:8983/solr/collection1/select?defType=edismax=AND=2=solar
> {quote}
> After Solr 5.5, the result will not be the same as Solr 5.4.
> [Solr 5.4]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> 0
>
> solr
>
>
>
>
> solar
> solar
>
> (+DisjunctionMaxQuerytext:so text:ol text:la text:ar)~2/no_coord
>
> +(((text:so text:ol text:la
> text:ar)~2))
> ...
>
> {code}
> [Solr 6.0.1]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> solar
> solar
>
> (+DisjunctionMaxQuery(((+text:so +text:ol +text:la +text:ar/no_coord
>
> +((+text:so +text:ol +text:la
> +text:ar))
> ...
> {code}
> As shown above, parsedquery also differs from Solr 5.4 and Solr 6.0.1(after
> Solr 5.5).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-9174) After Solr 5.5, mm parameter doesn't work properly
[
https://issues.apache.org/jira/browse/SOLR-9174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324426#comment-15324426
]
David Smiley commented on SOLR-9174:
bq. So I don't think you were "having it both ways"; rather, your explicit mm
spec was being ignored when you included explicit operators in queries against
Solr < 5.5.0.
That's much better said; yes. So if a user uses explicit operators, then I
think "mm" should be ignored. This was the case < 5.5.0 and it appears you
restored that today for 6.1. A better example may have been a "ipod AND power
AND nonexistentword" which should return nothing despite the 'mm'.
> After Solr 5.5, mm parameter doesn't work properly
> --
>
> Key: SOLR-9174
> URL: https://issues.apache.org/jira/browse/SOLR-9174
> Project: Solr
> Issue Type: Bug
> Components: query parsers, search
>Affects Versions: 5.5, 6.0, 6.0.1
>Reporter: Issei Nishigata
>
> “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]
> {code:xml}
>
>
> maxGramSize="2"/>
>
>
> {code}
> [request]
> {quote}
> http://localhost:8983/solr/collection1/select?defType=edismax=AND=2=solar
> {quote}
> After Solr 5.5, the result will not be the same as Solr 5.4.
> [Solr 5.4]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> 0
>
> solr
>
>
>
>
> solar
> solar
>
> (+DisjunctionMaxQuerytext:so text:ol text:la text:ar)~2/no_coord
>
> +(((text:so text:ol text:la
> text:ar)~2))
> ...
>
> {code}
> [Solr 6.0.1]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> solar
> solar
>
> (+DisjunctionMaxQuery(((+text:so +text:ol +text:la +text:ar/no_coord
>
> +((+text:so +text:ol +text:la
> +text:ar))
> ...
> {code}
> As shown above, parsedquery also differs from Solr 5.4 and Solr 6.0.1(after
> Solr 5.5).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-9174) After Solr 5.5, mm parameter doesn't work properly
[
https://issues.apache.org/jira/browse/SOLR-9174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323914#comment-15323914
]
Steve Rowe commented on SOLR-9174:
--
David, when I run your query against 5.4.1, it does indeed match 3 documents,
but I see two problems:
1. The parsedquery includes no minShouldMatch at all:
{noformat}
"parsedquery":"(+(DisjunctionMaxQuery((text:ipod))
(+DisjunctionMaxQuery((text:power))
+DisjunctionMaxQuery((text:nonexistentword)/no_coord",
{noformat}
2. The mm spec "2>-1" means: if there are two or fewer optional clauses, then
all clauses are required; if there are more than 2 optional clauses, then all
but one is required. In your query, there are only two optional clauses, so
both are required in the case that minShouldMatch applies.
By contrast, in 5.5.0, the parsedquery includes a minShouldMatch of 2:
{noformat}
"parsedquery":"(+((DisjunctionMaxQuery((text:ipod))
(+DisjunctionMaxQuery((text:power))
+DisjunctionMaxQuery((text:nonexistentword~2))/no_coord",
{noformat}
If I change the mm spec to "1>-1" (if more than one optional clause, then all
but one is required), then the parsedquery includes a minShouldMatch of 1, and
I get 3 hits.
So I don't think you were "having it both ways"; rather, your explicit mm spec
was being ignored when you included explicit operators in queries against Solr
< 5.5.0.
> After Solr 5.5, mm parameter doesn't work properly
> --
>
> Key: SOLR-9174
> URL: https://issues.apache.org/jira/browse/SOLR-9174
> Project: Solr
> Issue Type: Bug
> Components: query parsers, search
>Affects Versions: 5.5, 6.0, 6.0.1
>Reporter: Issei Nishigata
>
> “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]
> {code:xml}
>
>
> maxGramSize="2"/>
>
>
> {code}
> [request]
> {quote}
> http://localhost:8983/solr/collection1/select?defType=edismax=AND=2=solar
> {quote}
> After Solr 5.5, the result will not be the same as Solr 5.4.
> [Solr 5.4]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> 0
>
> solr
>
>
>
>
> solar
> solar
>
> (+DisjunctionMaxQuerytext:so text:ol text:la text:ar)~2/no_coord
>
> +(((text:so text:ol text:la
> text:ar)~2))
> ...
>
> {code}
> [Solr 6.0.1]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> solar
> solar
>
> (+DisjunctionMaxQuery(((+text:so +text:ol +text:la +text:ar/no_coord
>
> +((+text:so +text:ol +text:la
> +text:ar))
> ...
> {code}
> As shown above, parsedquery also differs from Solr 5.4 and Solr 6.0.1(after
> Solr 5.5).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-9174) After Solr 5.5, mm parameter doesn't work properly
[
https://issues.apache.org/jira/browse/SOLR-9174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15319232#comment-15319232
]
David Smiley commented on SOLR-9174:
In Solr 5.4 and before, you could use edismax like so (example assumes the
techproducts data):
http://localhost:8983/solr/techproducts/select?q=ipod+OR+(power+AND+nonexistentword)=json=true=true=edismax=2%3C-1=true=true
Notice that it is a query that shows that the user knows the search syntax.
And notice the mm allows 1 word to be optional.
If you run that query in 5.5 and forward, you get nothing.
> After Solr 5.5, mm parameter doesn't work properly
> --
>
> Key: SOLR-9174
> URL: https://issues.apache.org/jira/browse/SOLR-9174
> Project: Solr
> Issue Type: Bug
> Components: query parsers, search
>Affects Versions: 5.5, 6.0, 6.0.1
>Reporter: Issei Nishigata
>
> “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]
> {code:xml}
>
>
> maxGramSize="2"/>
>
>
> {code}
> [request]
> {quote}
> http://localhost:8983/solr/collection1/select?defType=edismax=AND=2=solar
> {quote}
> After Solr 5.5, the result will not be the same as Solr 5.4.
> [Solr 5.4]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> 0
>
> solr
>
>
>
>
> solar
> solar
>
> (+DisjunctionMaxQuerytext:so text:ol text:la text:ar)~2/no_coord
>
> +(((text:so text:ol text:la
> text:ar)~2))
> ...
>
> {code}
> [Solr 6.0.1]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> solar
> solar
>
> (+DisjunctionMaxQuery(((+text:so +text:ol +text:la +text:ar/no_coord
>
> +((+text:so +text:ol +text:la
> +text:ar))
> ...
> {code}
> As shown above, parsedquery also differs from Solr 5.4 and Solr 6.0.1(after
> Solr 5.5).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-9174) After Solr 5.5, mm parameter doesn't work properly
[
https://issues.apache.org/jira/browse/SOLR-9174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15318996#comment-15318996
]
Steve Rowe commented on SOLR-9174:
--
bq. I can't seem to have it both ways no matter what combo of parameters I use.
[~dsmiley], can you give an example of "having it both ways"?
> After Solr 5.5, mm parameter doesn't work properly
> --
>
> Key: SOLR-9174
> URL: https://issues.apache.org/jira/browse/SOLR-9174
> Project: Solr
> Issue Type: Bug
> Components: query parsers, search
>Affects Versions: 5.5, 6.0, 6.0.1
>Reporter: Issei Nishigata
>
> “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]
> {code:xml}
>
>
> maxGramSize="2"/>
>
>
> {code}
> [request]
> {quote}
> http://localhost:8983/solr/collection1/select?defType=edismax=AND=2=solar
> {quote}
> After Solr 5.5, the result will not be the same as Solr 5.4.
> [Solr 5.4]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> 0
>
> solr
>
>
>
>
> solar
> solar
>
> (+DisjunctionMaxQuerytext:so text:ol text:la text:ar)~2/no_coord
>
> +(((text:so text:ol text:la
> text:ar)~2))
> ...
>
> {code}
> [Solr 6.0.1]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> solar
> solar
>
> (+DisjunctionMaxQuery(((+text:so +text:ol +text:la +text:ar/no_coord
>
> +((+text:so +text:ol +text:la
> +text:ar))
> ...
> {code}
> As shown above, parsedquery also differs from Solr 5.4 and Solr 6.0.1(after
> Solr 5.5).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-9174) After Solr 5.5, mm parameter doesn't work properly
[
https://issues.apache.org/jira/browse/SOLR-9174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311167#comment-15311167
]
David Smiley commented on SOLR-9174:
This is definitely broken. The current situation is that you can only have
*ONE OF*:
* default AND but let users explicitly put "OR". No partial "mm" requirement.
To do this >= 5.5, set q.op=AND and mm=0%. (FWIW I kinda hate setting q.op or
df as it effects *all* filter queries, facet queries, etc. not just 'q')
* mm of something other than 0%. To do this, set mm as desired; q.op won't
matter.
I can't seem to have it both ways no matter what combo of parameters I use. I
could have it both ways prior to 5.5 easily enough by, if I recall, setting
mm=whatever and let q.op default to OR.
bq. I understood that q.op overrides mm. Is my understanding mentioned above
right?
No, the other way around.
> After Solr 5.5, mm parameter doesn't work properly
> --
>
> Key: SOLR-9174
> URL: https://issues.apache.org/jira/browse/SOLR-9174
> Project: Solr
> Issue Type: Bug
> Components: query parsers, search
>Affects Versions: 5.5, 6.0, 6.0.1
>Reporter: Issei Nishigata
>
> “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]
> {code:xml}
>
>
> maxGramSize="2"/>
>
>
> {code}
> [request]
> {quote}
> http://localhost:8983/solr/collection1/select?defType=edismax=AND=2=solar
> {quote}
> After Solr 5.5, the result will not be the same as Solr 5.4.
> [Solr 5.4]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> 0
>
> solr
>
>
>
>
> solar
> solar
>
> (+DisjunctionMaxQuerytext:so text:ol text:la text:ar)~2/no_coord
>
> +(((text:so text:ol text:la
> text:ar)~2))
> ...
>
> {code}
> [Solr 6.0.1]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> solar
> solar
>
> (+DisjunctionMaxQuery(((+text:so +text:ol +text:la +text:ar/no_coord
>
> +((+text:so +text:ol +text:la
> +text:ar))
> ...
> {code}
> As shown above, parsedquery also differs from Solr 5.4 and Solr 6.0.1(after
> Solr 5.5).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-9174) After Solr 5.5, mm parameter doesn't work properly
[
https://issues.apache.org/jira/browse/SOLR-9174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310477#comment-15310477
]
Issei Nishigata commented on SOLR-9174:
---
I think I misunderstood the behavior of {{mm}}.
In this particular case, it seems that I can also get expected result by the
{{q.op=OR}}.
As a matter of fact, it does have no meaning that I mixed up {{q.op}} and
{{mm}} together.
I have confirmed that {{q.op}} is interpreted {{mm}} in the source code.
I understood that {{q.op}} overrides {{mm}}.
Is my understanding mentioned above right?
> After Solr 5.5, mm parameter doesn't work properly
> --
>
> Key: SOLR-9174
> URL: https://issues.apache.org/jira/browse/SOLR-9174
> Project: Solr
> Issue Type: Bug
> Components: query parsers, search
>Affects Versions: 5.5, 6.0, 6.0.1
>Reporter: Issei Nishigata
>
> “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]
> {code:xml}
>
>
> maxGramSize="2"/>
>
>
> {code}
> [request]
> {quote}
> http://localhost:8983/solr/collection1/select?defType=edismax=AND=2=solar
> {quote}
> After Solr 5.5, the result will not be the same as Solr 5.4.
> [Solr 5.4]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> 0
>
> solr
>
>
>
>
> solar
> solar
>
> (+DisjunctionMaxQuerytext:so text:ol text:la text:ar)~2/no_coord
>
> +(((text:so text:ol text:la
> text:ar)~2))
> ...
>
> {code}
> [Solr 6.0.1]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> solar
> solar
>
> (+DisjunctionMaxQuery(((+text:so +text:ol +text:la +text:ar/no_coord
>
> +((+text:so +text:ol +text:la
> +text:ar))
> ...
> {code}
> As shown above, parsedquery also differs from Solr 5.4 and Solr 6.0.1(after
> Solr 5.5).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-9174) After Solr 5.5, mm parameter doesn't work properly
[
https://issues.apache.org/jira/browse/SOLR-9174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15308597#comment-15308597
]
Jan Høydahl commented on SOLR-9174:
---
As long as you set mm, you should not need to set q.op. But there seems to be a
bug leading to q.op=AND overriding mm in some cases, so just try your
particular use case with q.op=OR and report back your findings. I'm afraid you
may end up with other queries not working the way you intended with q.op=OR :(
> After Solr 5.5, mm parameter doesn't work properly
> --
>
> Key: SOLR-9174
> URL: https://issues.apache.org/jira/browse/SOLR-9174
> Project: Solr
> Issue Type: Bug
> Components: query parsers, search
>Affects Versions: 5.5, 6.0, 6.0.1
>Reporter: Issei Nishigata
>
> “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]
> {code:xml}
>
>
> maxGramSize="2"/>
>
>
> {code}
> [request]
> {quote}
> http://localhost:8983/solr/collection1/select?defType=edismax=AND=2=solar
> {quote}
> After Solr 5.5, the result will not be the same as Solr 5.4.
> [Solr 5.4]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> 0
>
> solr
>
>
>
>
> solar
> solar
>
> (+DisjunctionMaxQuerytext:so text:ol text:la text:ar)~2/no_coord
>
> +(((text:so text:ol text:la
> text:ar)~2))
> ...
>
> {code}
> [Solr 6.0.1]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> solar
> solar
>
> (+DisjunctionMaxQuery(((+text:so +text:ol +text:la +text:ar/no_coord
>
> +((+text:so +text:ol +text:la
> +text:ar))
> ...
> {code}
> As shown above, parsedquery also differs from Solr 5.4 and Solr 6.0.1(after
> Solr 5.5).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-9174) After Solr 5.5, mm parameter doesn't work properly
[
https://issues.apache.org/jira/browse/SOLR-9174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15308589#comment-15308589
]
Jan Høydahl commented on SOLR-9174:
---
There is a long history here. Back in the days, (e)dismax did only care about
{{mm}}, which defaulted to {{100%}}. Then people got confused when they had
{{q.op=OR}} or {{defaultOperator=OR}} in the schema, so we added some logic
{{if q.op==OR then mm=0 else mm=100%}} which kicked in *if user did not
explicitly set mm*.
But then there was the case of explicit operators in the query, which pre-5.5
used to ignore {{mm}} completely, see SOLR-2649. So in 5.5 we tried to solve
that one, changing the interaction between {{q.op}} and {{mm}} a bit, leading
to SOLR-8812, and perhaps also the root case for this issue?
> After Solr 5.5, mm parameter doesn't work properly
> --
>
> Key: SOLR-9174
> URL: https://issues.apache.org/jira/browse/SOLR-9174
> Project: Solr
> Issue Type: Bug
> Components: query parsers, search
>Affects Versions: 5.5, 6.0, 6.0.1
>Reporter: Issei Nishigata
>
> “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]
> {code:xml}
>
>
> maxGramSize="2"/>
>
>
> {code}
> [request]
> {quote}
> http://localhost:8983/solr/collection1/select?defType=edismax=AND=2=solar
> {quote}
> After Solr 5.5, the result will not be the same as Solr 5.4.
> [Solr 5.4]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> 0
>
> solr
>
>
>
>
> solar
> solar
>
> (+DisjunctionMaxQuerytext:so text:ol text:la text:ar)~2/no_coord
>
> +(((text:so text:ol text:la
> text:ar)~2))
> ...
>
> {code}
> [Solr 6.0.1]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> solar
> solar
>
> (+DisjunctionMaxQuery(((+text:so +text:ol +text:la +text:ar/no_coord
>
> +((+text:so +text:ol +text:la
> +text:ar))
> ...
> {code}
> As shown above, parsedquery also differs from Solr 5.4 and Solr 6.0.1(after
> Solr 5.5).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-9174) After Solr 5.5, mm parameter doesn't work properly
[
https://issues.apache.org/jira/browse/SOLR-9174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15308266#comment-15308266
]
Ahmet Arslan commented on SOLR-9174:
Can someone explain why (e)dismax should honor/respect/care the {{q.op}}
parameter?
(e)dismax has its own parameter {{mm}} for the task.
> After Solr 5.5, mm parameter doesn't work properly
> --
>
> Key: SOLR-9174
> URL: https://issues.apache.org/jira/browse/SOLR-9174
> Project: Solr
> Issue Type: Bug
> Components: query parsers, search
>Affects Versions: 5.5, 6.0, 6.0.1
>Reporter: Issei Nishigata
>
> “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]
> {code:xml}
>
>
> maxGramSize="2"/>
>
>
> {code}
> [request]
> {quote}
> http://localhost:8983/solr/collection1/select?defType=edismax=AND=2=solar
> {quote}
> After Solr 5.5, the result will not be the same as Solr 5.4.
> [Solr 5.4]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> 0
>
> solr
>
>
>
>
> solar
> solar
>
> (+DisjunctionMaxQuerytext:so text:ol text:la text:ar)~2/no_coord
>
> +(((text:so text:ol text:la
> text:ar)~2))
> ...
>
> {code}
> [Solr 6.0.1]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> solar
> solar
>
> (+DisjunctionMaxQuery(((+text:so +text:ol +text:la +text:ar/no_coord
>
> +((+text:so +text:ol +text:la
> +text:ar))
> ...
> {code}
> As shown above, parsedquery also differs from Solr 5.4 and Solr 6.0.1(after
> Solr 5.5).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-9174) After Solr 5.5, mm parameter doesn't work properly
[
https://issues.apache.org/jira/browse/SOLR-9174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15308192#comment-15308192
]
Issei Nishigata commented on SOLR-9174:
---
Thank you for your suggestion.
Is q.op=OR completely replaceable with q.op=AND parameter?
Is the result with q.op=OR perfectly identical with the result with q.op=AND
parameter
as long as mm parameter is used, even under different condition such that there
are multiple search words?
If so, I will use q.op=OR tentatively.
> After Solr 5.5, mm parameter doesn't work properly
> --
>
> Key: SOLR-9174
> URL: https://issues.apache.org/jira/browse/SOLR-9174
> Project: Solr
> Issue Type: Bug
> Components: query parsers, search
>Affects Versions: 5.5, 6.0, 6.0.1
>Reporter: Issei Nishigata
>
> “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]
> {code:xml}
>
>
> maxGramSize="2"/>
>
>
> {code}
> [request]
> {quote}
> http://localhost:8983/solr/collection1/select?defType=edismax=AND=2=solar
> {quote}
> After Solr 5.5, the result will not be the same as Solr 5.4.
> [Solr 5.4]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> 0
>
> solr
>
>
>
>
> solar
> solar
>
> (+DisjunctionMaxQuerytext:so text:ol text:la text:ar)~2/no_coord
>
> +(((text:so text:ol text:la
> text:ar)~2))
> ...
>
> {code}
> [Solr 6.0.1]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> solar
> solar
>
> (+DisjunctionMaxQuery(((+text:so +text:ol +text:la +text:ar/no_coord
>
> +((+text:so +text:ol +text:la
> +text:ar))
> ...
> {code}
> As shown above, parsedquery also differs from Solr 5.4 and Solr 6.0.1(after
> Solr 5.5).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-9174) After Solr 5.5, mm parameter doesn't work properly
[
https://issues.apache.org/jira/browse/SOLR-9174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15307383#comment-15307383
]
Jan Høydahl commented on SOLR-9174:
---
As a workaround you could try to set q.op=OR
> After Solr 5.5, mm parameter doesn't work properly
> --
>
> Key: SOLR-9174
> URL: https://issues.apache.org/jira/browse/SOLR-9174
> Project: Solr
> Issue Type: Bug
> Components: query parsers, search
>Affects Versions: 5.5, 6.0, 6.0.1
>Reporter: Issei Nishigata
>
> “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]
> {code:xml}
>
>
> maxGramSize="2"/>
>
>
> {code}
> [request]
> {quote}
> http://localhost:8983/solr/collection1/select?defType=edismax=AND=2=solar
> {quote}
> After Solr 5.5, the result will not be the same as Solr 5.4.
> [Solr 5.4]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> 0
>
> solr
>
>
>
>
> solar
> solar
>
> (+DisjunctionMaxQuerytext:so text:ol text:la text:ar)~2/no_coord
>
> +(((text:so text:ol text:la
> text:ar)~2))
> ...
>
> {code}
> [Solr 6.0.1]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> solar
> solar
>
> (+DisjunctionMaxQuery(((+text:so +text:ol +text:la +text:ar/no_coord
>
> +((+text:so +text:ol +text:la
> +text:ar))
> ...
> {code}
> As shown above, parsedquery also differs from Solr 5.4 and Solr 6.0.1(after
> Solr 5.5).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
