[
https://issues.apache.org/jira/browse/SOLR-10527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975772#comment-15975772
]
ASF subversion and git services commented on SOLR-10527:
--------------------------------------------------------
Commit f577562a647c26af28110c168d8d62d8c2a2fa34 in lucene-solr's branch
refs/heads/branch_6x from [~steve_rowe]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=f577562 ]
SOLR-10527: move CHANGES entry to 6.5.1 section
> edismax with sow=false fails to create dismax-per-term queries when any field
> is boosted
> ----------------------------------------------------------------------------------------
>
> Key: SOLR-10527
> URL: https://issues.apache.org/jira/browse/SOLR-10527
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Steve Rowe
> Fix For: 6.6, master (7.0)
>
> Attachments: SOLR-10527.patch
>
>
> When {{sow=false}}, the edismax query parser creates dismax-per-field queries
> when field analysis is different enough that query structures differ per
> field (stopwords in one field only, e.g.). (By contrast, dismax-per-*term*
> queries are produced when {{sow=true}} or when query structures are the same
> across all fields.)
> However, the code to determine whether per-field query structures differed
> wasn't aware of boost queries. As a result, when {{sow=false}} and boost are
> specified for at least one field (e.g. {{q=\{!edismax
> sow=false\}text&qf=fieldA^2+fieldB^4}}), dismax-per-field queries are always
> produced, even when per-field query structures are equivalent.
--
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
