jpountz commented on issue #14669: URL: https://github.com/apache/lucene/issues/14669#issuecomment-2897936261
I wonder if this use-case would be better served by something like Elasticsearch's shard request cache. The cache key is the whole request (query, number of hits retrieved, etc.), plus an identifier of the current point-in-time view of the top-level index reader, and it caches the whole result. So it invalidates more frequently than the query cache (on every refresh), but it is also safe, including for things that have inter-segment dependencies, such as BM25 scores which are computed on global term statistics, or vector search where whether a document is a top-hit depends on whether other segments have better hits or not. -- 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
