MultiCollector collect behavior is changed

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

MultiCollector collect behavior is changed

Yonghui Zhao
In lucene 4.10,
If one collector throw CollectionTerminatedException,  all collectors are
terminated.

In lucene 7.2.1, CollectionTerminatedException will only terminate current
collector,  the others won't be terminated.


How to keep old behavior?
Reply | Threaded
Open this post in threaded view
|

Re: MultiCollector collect behavior is changed

Adrien Grand
This was considered a bug as the need to early-terminate is a per-collector
decision. If you want to do something like that again, you could fork
MultiCollector and propagate CollectionTerminatedExceptions.

Le mer. 4 juil. 2018 à 05:34, Yonghui Zhao <[hidden email]> a écrit :

> In lucene 4.10,
> If one collector throw CollectionTerminatedException,  all collectors are
> terminated.
>
> In lucene 7.2.1, CollectionTerminatedException will only terminate current
> collector,  the others won't be terminated.
>
>
> How to keep old behavior?
>
Reply | Threaded
Open this post in threaded view
|

Re: MultiCollector collect behavior is changed

Yonghui Zhao
Thanks Adrien, got it.

2018-07-04 13:46 GMT+08:00 Adrien Grand <[hidden email]>:

> This was considered a bug as the need to early-terminate is a per-collector
> decision. If you want to do something like that again, you could fork
> MultiCollector and propagate CollectionTerminatedExceptions.
>
> Le mer. 4 juil. 2018 à 05:34, Yonghui Zhao <[hidden email]> a
> écrit :
>
> > In lucene 4.10,
> > If one collector throw CollectionTerminatedException,  all collectors are
> > terminated.
> >
> > In lucene 7.2.1, CollectionTerminatedException will only terminate
> current
> > collector,  the others won't be terminated.
> >
> >
> > How to keep old behavior?
> >
>