[GitHub] [lucene] benwtrent commented on pull request #12118: Add `FeatureQuery` weight caching in non-scoring case

["benwtrent (via GitHub)" <gi...@apache.org>]

benwtrent commented on PR #12118:
URL: https://github.com/apache/lucene/pull/12118#issuecomment-1410402325

   @rmuir 
   
   > i don't understand this issue. The only purpose of this query is for scoring. If you don't want scores, drop the clause completely.
   
   A `FeatureField` provides a useful extension point for learned-sparse retrieval models (see linked issue). These models provide multiple `feature` and `score` pairs. These fields will likely match relevant documents that are not previously matched by other means.
   
   A perfectly valid (and powerful) query would be `BooleanQuery` with multiple `SHOULD` clauses containing `FeatureQuery` objects (obviously, with minimum should match > 0). Note that no other field is being queried. Dropping all those clauses would be a `match_all` and not accurately reflect the matching document set.
   
   Being able to iterate the entire recall set for matching multiple `FeatureField` values will provide useful insight.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org