[ https://issues.apache.org/jira/browse/LUCENE-8490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan Woodward resolved LUCENE-8490. ----------------------------------- Resolution: Won't Fix I'm still not happy with the API, but I don't think my proposed change here makes things any better so am closing for now. > 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org