Hi ,
We have a index that has multiple segments generated with continuous
updates. There is always a large dominant segment after index rebuild,
then many small segments are generated with continuous updates. At query
time we apply early termination with EarlyTerminatingCollector
https://github.
If it had some more intelligence it would not be a bad feature. The
alternative for users working with very large systems is complicated
scripting.
On Thu, May 11, 2023 at 4:09 AM Jan Høydahl wrote:
> I didn't know about this multi delete either, it must have been introduced
> for a reason? If y
I didn't know about this multi delete either, it must have been introduced for
a reason? If you e.g. want to reduce "replicationFactor" from 5 to 3, it will
not work to update collectionProp "replicationFactor", not even the individual
num props. That would be the natural way for this feature to
