[
https://issues.apache.org/jira/browse/LUCENE-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542675
]
Sean Timm commented on LUCENE-997:
----------------------------------
> I think my preference for the API and implementation would be in
> HitCollector.collect()
This would be simpler, but I don't see how it would be possible to estimate the
total number of results and return partial results in that case. I think that
is an important feature.
If the concern is complexity for the application, perhaps it is possible to
hide the TimerThread altogether. The TimerThread could be created and started
via a searcher setTimeOut(tick, numTicks) method.
To simplify it further, ticks could be fixed at a reasonable number, e.g., 100
ms, and a timeout in milliseconds could be passed in: setTimeout(milliseconds).
> Add search timeout support to Lucene
> ------------------------------------
>
> Key: LUCENE-997
> URL: https://issues.apache.org/jira/browse/LUCENE-997
> Project: Lucene - Java
> Issue Type: New Feature
> Reporter: Sean Timm
> Priority: Minor
> Attachments: LuceneTimeoutTest.java, timeout.patch, timeout.patch
>
>
> This patch is based on Nutch-308.
> This patch adds support for a maximum search time limit. After this time is
> exceeded, the search thread is stopped, partial results (if any) are returned
> and the total number of results is estimated.
> This patch tries to minimize the overhead related to time-keeping by using a
> version of safe unsynchronized timer.
> This was also discussed in an e-mail thread.
> http://www.nabble.com/search-timeout-tf3410206.html#a9501029
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
