[
https://issues.apache.org/jira/browse/LUCENE-8490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16607618#comment-16607618
]
David Smiley commented on LUCENE-8490:
--------------------------------------
+1 to the overall idea of making a "purely scoring queries" a first class
citizen.
I've been concerned about BooleanQuery doing too much (IMO), and your proposal
would make it do yet one more thing. Hmmm. I'll look at your patch later.
Peer review will be important on such an impactful change.
> 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: [email protected]
For additional commands, e-mail: [email protected]
