[
https://issues.apache.org/jira/browse/LUCENE-8143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351662#comment-17351662
]
Alan Woodward commented on LUCENE-8143:
---------------------------------------
Now that Spans are in the queries module this seems like a good time to revisit
this. [~dsmiley] I think that removing is the correct call here? If we change
things so that boosts get applied differently then existing queries are going
to silently change their scores in unexpected ways, whereas if we remove then
users will get compilation errors when upgrading and we can point them to a
vanilla BoostQuery for top-level boosts.
> Remove SpanBoostQuery
> ---------------------
>
> Key: LUCENE-8143
> URL: https://issues.apache.org/jira/browse/LUCENE-8143
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Adrien Grand
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I initially added it so that span queries could still be boosted, but this
> was actually a mistake: boosts are ignored on inner span queries, only the
> boost of the top-level span query, the one that performs scoring, is not
> ignored.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
