Which shows you how good my memory is .
Thinking about it, of course, the HitCollectors *naturally*
go to completion if collecting the top scoring documents
is going to work since the last document examined
may be the top scoring one.
Ah well, shows you how my brain works on vacation
Thanks
Erick
>
> Ok, I'm not near any documentation now, but I think
> throwing an exception is overkill. As I remember
> all you have to do is return false from your collector
> and that'll stop the search. But verify that.
>
That would have been much cleaner, however collect() is a void,
so throwing a (runti
ssage d'origine ----
> De : Andrzej Bialecki <[EMAIL PROTECTED]>
> À : java-user@lucene.apache.org
> Envoyé le : Jeudi, 7 Août 2008, 14h29mn 31s
> Objet : Re: Stop search process when a given number of hits is reached
>
> Doron Cohen wrote:
> > Nothing built
Re: Stop search process when a given number of hits is reached
Doron Cohen wrote:
> Nothing built in that I'm aware of will do this, but it can be done by
> searching with your own HitCollector.
> There is a related feature - stop search after a specified time - using
> TimeLimite
Doron Cohen wrote:
Nothing built in that I'm aware of will do this, but it can be done by
searching with your own HitCollector.
There is a related feature - stop search after a specified time - using
TimeLimitedCollector.
It is not released yet, see issue LUCENE-997.
In short, the collector's col
Nothing built in that I'm aware of will do this, but it can be done by
searching with your own HitCollector.
There is a related feature - stop search after a specified time - using
TimeLimitedCollector.
It is not released yet, see issue LUCENE-997.
In short, the collector's collect() method is invo
