Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Won't Fix
-
None
-
None
-
None
-
None
-
New
Description
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.