Thanks a lot.
I tried to debug a long query and see when it gets to the collector.
I thought it will be better to catch the "stop" action in the search itself
and not the top doc collector as I would assume the search action will take
long time to finish and once we get to the top doc collector,
The simplest way would be a CollectorDelegate that wraps an existing
collector and checks a boolean before calling the delegates collect
method.
simon
On Mon, May 23, 2011 at 8:09 AM, liat oren wrote:
> Thank you very much.
>
> So the best solution would be to implement the collector with a stop
Thank you very much.
So the best solution would be to implement the collector with a stop
function.
Do you happen to have an example for that?
Many thanks,
Liat
On 22 May 2011 13:19, Simon Willnauer wrote:
> On Sun, May 22, 2011 at 4:48 PM, Devon H. O'Dell
> wrote:
> > I have my own collector,
On Sun, May 22, 2011 at 4:48 PM, Devon H. O'Dell wrote:
> I have my own collector, but implemented this functionality by running
> the search in a thread pool and terminating the FutureTask running the
> job if it took longer than some configurable amount of time. That
> seemed to do the trick for
I have my own collector, but implemented this functionality by running
the search in a thread pool and terminating the FutureTask running the
job if it took longer than some configurable amount of time. That
seemed to do the trick for me. (In my case, the IndexReader is
explicitly opened readonly,
you can impl. you own collector and notify the collector to stop if you need to.
simon
On Sun, May 22, 2011 at 12:06 PM, liat oren wrote:
> Hi Everyone,
>
> Is there a way to stop a multi search in the middle?
>
> Thanks a lot,
> Liat
>
---
Hi Everyone,
Is there a way to stop a multi search in the middle?
Thanks a lot,
Liat
