[
https://issues.apache.org/jira/browse/LUCENE-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538144
]
Lance Norskog commented on LUCENE-997:
--------------------------------------
I stumbled above; I do not yet know Jira :) The Solr code is SOLR-392.
This request is inspired by a public search engine with millions of records.
There are three different aspects mentioned above that can cause a query to
"go rogue": timing out, finding too many records to give a truly useable
result, and using up too much memory. The point is that if a search is going to
find 14 million hits, Google does not go and tally them. It stops quickly and
estimates how many might remain. I would like to have similar control.
The HitCollector implementation mentioned above would allow all three of these
control options. If they could be pipelined together we could use any or all of
them.
> 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]
