vigyasharma commented on PR #14729:
URL: https://github.com/apache/lucene/pull/14729#issuecomment-2926680983

   > This sounds like it would fit nicely with the `Rescorer` infrastructure?
   
   I wasn't aware of Query Rescorers, thanks @romseygeek for pointing me in 
that direction. At the outset, it seems like we could create a 
`DoubleValuesSourceRescorer extends Rescorer`  – that rescores based on the 
`DoubleValuesSource` instead of a second query.
   
   However, this is exactly what the `FunctionScoreQuery` does, and the 
benefits of one over the other are not immediately obvious to me. I 
see`FunctionScoreQuery` being a `Query`, exposes a `SegmentCacheable` weight, 
which could be useful? Though I believe we only cache hits (disi) and not 
scores, so maybe it doesn't matter for this use case?
   
   Do you see any benefits to using `Rescorer` over `FunctionScoreQuery` ?


-- 
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-unsubscr...@lucene.apache.org

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


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

Reply via email to