[
https://issues.apache.org/jira/browse/SOLR-8164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14969230#comment-14969230
]
Erik Hatcher commented on SOLR-8164:
------------------------------------
[~yo...@apache.org] - good fix, thanks. But, how about a test case to go along
with this? Always good to increase test coverage when a "Bug" is found.
> Debug "parsedquery" output no longer handles boosts correctly
> -------------------------------------------------------------
>
> Key: SOLR-8164
> URL: https://issues.apache.org/jira/browse/SOLR-8164
> Project: Solr
> Issue Type: Bug
> Reporter: Yonik Seeley
> Assignee: Yonik Seeley
> Priority: Minor
> Fix For: Trunk
>
> Attachments: SOLR-8164.patch
>
>
> Since Lucene's removal of boosts on every query, Solr's debug output has been
> somewhat broken.
> {code}
> http://localhost:8983/solr/techproducts/query?debugQuery=true&q=(foo_s:a^3)^4
> shows "parsedquery":"BoostQuery(foo_s:a^3.0)",
> and
> http://localhost:8983/solr/techproducts/query?debugQuery=true&q=foo_s:a^=2
> shows "parsedquery":"ConstantScore(foo_s:a)",
> {code}
> Since boosts are now explicit (i.e. BoostQuery), we should probably just move
> to always showing boosts instead of having logic that tries to be smart about
> it.
--
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
