You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by GitBox <gi...@apache.org> on 2022/06/03 08:02:46 UTC

[GitHub] [lucene] gsmiller commented on pull request #927: LUCENE-10151: Adding Timeout Support to IndexSearcher

gsmiller commented on PR #927:
URL: https://github.com/apache/lucene/pull/927#issuecomment-1145702837

   @jpountz I'd be curious to hear your thoughts on asking the user to specify the timeout as a future point-in-time where the search will be halted (as you're suggesting above) vs. allowing the user to specify the amount of time they want to allow searches to run. If we did the later, users wouldn't need to instantiate new instances of `IndexSearcher` for each query (instead, `IndexSearcher` could internally compute the future point-in-time to timeout based on the user-specified allotted time and "now"). Is your thinking that it might be a common use-case for users to want to allow for different amounts of execution time for different queries?


-- 
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