You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Alan Woodward (JIRA)" <ji...@apache.org> on 2018/09/07 08:31:00 UTC
[jira] [Commented] (LUCENE-8490) Separate scoring features from
Queries
[ https://issues.apache.org/jira/browse/LUCENE-8490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606837#comment-16606837 ]
Alan Woodward commented on LUCENE-8490:
---------------------------------------
Here's a preliminary patch outlining the idea.
* I've called the base class Feature, but maybe something that includes a reference to score or boost might be better?
* This is aimed at lucene 8 and just cuts everything over to the new class hierarchy, but it would be simple enough to add deprecations using a query wrapper if we wanted to get it into the 7x series
> Separate scoring features from Queries
> --------------------------------------
>
> Key: LUCENE-8490
> URL: https://issues.apache.org/jira/browse/LUCENE-8490
> Project: Lucene - Core
> Issue Type: New Feature
> Reporter: Alan Woodward
> Assignee: Alan Woodward
> Priority: Major
> Attachments: LUCENE-8490.patch
>
>
> We currently have two types of 'purely scoring' queries, produced by static methods on FeatureField and more recently on LongPoint (for distance or recency boosting). These don't really make sense as standalone queries, and are designed to be used as supplementary SHOULD clauses in boolean queries. I think these would be easier to use (and would prevent misuses, such as using them in FILTER or MUST clauses) if we designated them as Features instead, with a separate class hierarchy, and add a specific feature() method to BooleanQuery.Builder.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org