[
https://issues.apache.org/jira/browse/LUCENE-8099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16312867#comment-16312867
]
Alan Woodward commented on LUCENE-8099:
---------------------------------------
I committed those extra static methods, and improved the javadocs and migration
messages.
Re performance: there shouldn't be any reason for things to be slower, and
FunctionScoreQuery is fully integrated with things like two-phase iteration, so
should if anything be faster than the queries it's replacing.
DoubleValuesSource is iterator based and handles things like existence checks
with fewer branches than ValueSource; same with Expressions, which are compiled
to java bytecode. It might be useful to add some examples of these queries to
the benchmark tests though.
> Deprecate CustomScoreQuery, BoostedQuery and BoostingQuery
> ----------------------------------------------------------
>
> Key: LUCENE-8099
> URL: https://issues.apache.org/jira/browse/LUCENE-8099
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Alan Woodward
> Assignee: Alan Woodward
> Priority: Minor
> Fix For: 7.3
>
> Attachments: LUCENE-8099-2.patch, LUCENE-8099.patch, LUCENE-8099.patch
>
>
> After LUCENE-7998, these three queries can all be replaced by a
> FunctionScoreQuery. Using lucene-expressions makes them much easier to use
> as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
