Sorry, I see that it may have been confusing.
My webapp calls the reload of all the affected Collections (about a dozen
of them) in sequential mode using the Collections API.
Ideally I would be able to write some QueryTimeSynonymFilterFactory that
would periodically or when told, reload the synonym's file from ZK, which
is what the system edits when a user changes some synonyms.
I understand that a Collection needs to be reloaded if the synonyms were to
be used at indexation time, but this is not my case.
The managed API is on the same situation, basically it does what I am doing
on my own right now. At the end, there has to be a reload of the affected
Collections.
Regards,
Simón
On Sun, Dec 30, 2018 at 5:01 AM Shawn Heisey wrote:
> On 12/29/2018 5:55 AM, Simón de Frosterus Pokrzywnicki wrote:
> > The problem is that when the user changes the synonyms, it automatically
> > triggers a sequential reload of all the Collections.
>
> What exactly is being done when you say "the user changes the
> synonyms"? Just uploading a new synonyms definition file to zookeeper
> would *NOT* result in a reload of *ANY* collection. As far as I am
> aware, collection reloads only happen when they are explicitly
> requested. Usage of the managed APIs to change aspects of the schema
> could cause a reload, but it's only going to happen on the collection
> where the API is used, not all collections.
>
> Basically, I cannot imagine any situation that would cause a reload of
> all collections, other than explicitly asking Solr to do those reloads.
>
> Thanks,
> Shawn
>
>
