In standard Lucene this information is not stored, but I wrapped the
default MergePolicy to be able to store the merged segments.
It works great, except for point-in-time merges occurring during segment
flush.
Le 16/12/2024 à 16:31, David Smiley a écrit :
Not sure if the segment metadata cont
Not sure if the segment metadata contains merge info on what segments it
merged. I suppose that's what you'd like. You might be able to add such
metadata; not sure.
On Mon, Dec 16, 2024 at 8:50 AM Cédric Damioli wrote:
> Hi David,
>
>
> Le 15/12/2024 à 18:50, David Smiley a écrit :
> > Hi Cedr
Hi David,
Le 15/12/2024 à 18:50, David Smiley a écrit :
Hi Cedric,
On Fri, Dec 13, 2024 at 6:38 PM Cédric Damioli wrote:
Is there a way to listen to such
behaviour or to have a callback called ?
On this point I'm unclear what the problem is. Why does it matter that
your listener doesn't
Hi Cedric,
On Fri, Dec 13, 2024 at 6:38 PM Cédric Damioli wrote:
> Could you tell me if the observed behaviour is definitely normal and
> that I should learn to deal with it ?
Yes.
> Is there a way to listen to such
> behaviour or to have a callback called ?
>
On this point I'm unclear what
Hi,
I encountered weird race conditions when playing with MergePolicy and
various cache-related SolrEventListener and I don't even know if it's a
bug or a feature that I should compose with. I don't event know if my
question actually belong to this list (it begins with Lucene stuff and
ends w
