Nikolay Martynov created SOLR-10442:
---------------------------------------
Summary: xtendedDismaxQParser (edismax) makes pf* require search
term exactly
Key: SOLR-10442
URL: https://issues.apache.org/jira/browse/SOLR-10442
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Components: query parsers
Affects Versions: 6.5
Reporter: Nikolay Martynov
Request like:
{code}
"params":{
"q": "cat AND dog",
"q.op": "AND",
"defType":"edismax",
"qf":"description",
"pf2":"description"
}
{code}
produces query like this:
{code}
"parsedquery_toString":"+(+(description.en:cat) +(description.en:dog))
(+(description.en:\"cat dog\"))"
{code}
Solr 4.6.1 produces different parsing of this query:
{code}
"parsedquery_toString": "+(+(description.en:cat) +(description.en:dog))
(description.en:\"cat dog\")",
{code}
Replacing {{q.op=AND}} with {{q.op=OR}} in newer Solr produces same query as
old Solr despite the fact that it would seem that this change should not make a
difference.
This issue is probably related to SOLR-8812 - looks like it is just one more
case of same problem. It also would mean that change occurred in version range
specified there - unfortunately I would not be able to test that.
This looks like a change in behaviour is not quite expected: now introducing
pf2 searches for documents that must have 'cat dog' phrase instead of just
boosting such documents.
Please let me know if more information is required.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
