ManagedSynonymFilterFactory per core instead of config set?

[Georg Sorst <g....@findologic.com>]

Hi list!

Is it possible to set synonyms per core when using
the ManagedSynonymFilterFactory, even when using config sets?

What makes me think that this is not possible is that the synonyms are
stored in
$solr_home/configsets/$config_set/conf/_schema_analysis_synonyms_$resource.json.
So when I add some synonyms to core A (which uses $config_set) and then
create core B (which also uses $config_set), then core B will have the same
synonyms as core A. I have validated this by GETing the synonyms for core B.

Am I doing something wrong, or is this on purpose? Is there a way to manage
synonyms per core? Should I use a differente value for $resource for each
core?

Thanks!
Georg
-- 
*Georg M. Sorst I CTO*
FINDOLOGIC GmbH



Jakob-Haringer-Str. 5a | 5020 Salzburg I T.: +43 662 456708
E.: g.sorst@findologic.com
www.findologic.com Folgen Sie uns auf: XING
<https://www.xing.com/profile/Georg_Sorst>facebook
<https://www.facebook.com/Findologic> Twitter
<https://twitter.com/findologic>

Wir sehen uns auf dem *Shopware Community Day in Ahaus am 20.05.2016!* Hier
<beratung@findologic.com?subject=Terminvereinbarung%20SCD> Termin
vereinbaren!
Wir sehen uns auf der* dmexco in Köln am 14.09. und 15.09.2016!* Hier
<beratung@findologic.com?subject=Terminvereinbarung%20dmexco> Termin
vereinbaren!

Re: ManagedSynonymFilterFactory per core instead of config set?

[Erick Erickson <er...@gmail.com>]

The managed schema stuff is changing the configset
copy by design, not the individual core's synonyms
so you are correct, you can't at this point have
different synonyms per core if those cores are using
the same configset.

Best,
Erick

On Sun, Apr 17, 2016 at 7:57 AM, Shawn Heisey <ap...@elyograg.org> wrote:
> On 4/17/2016 8:00 AM, Georg Sorst wrote:
>> Am I doing something wrong, or is this on purpose? Is there a way to manage
>> synonyms per core? Should I use a differente value for $resource for each
>> core?
>
> If you want different configs for each core, don't use configsets.  Each
> core will need its own conf directory with its own config, which can be
> different from every other config.
>
> One of the advancements in SolrCloud is the idea of shared configs.
> Every core (shard replica) in a collection pulls exactly the same config
> from zookeeper.  That config can be shared between multiple collections
> running on multiple servers, so a change in the shared config will
> affect all linked collections once they are reloaded.
>
> The configsets feature (which was first available in Solr 4.8) is
> intended to bring that same shared configuration to systems NOT running
> in cloud mode, but it can only do so for cores on a single machine,
> unlike SolrCloud.  By using configsets, you have told Solr that you
> *want* the exact same config on multiple cores on that server.
>
> Thanks,
> Shawn
>

Re: ManagedSynonymFilterFactory per core instead of config set?

[Shawn Heisey <ap...@elyograg.org>]

On 4/17/2016 8:00 AM, Georg Sorst wrote:
> Am I doing something wrong, or is this on purpose? Is there a way to manage
> synonyms per core? Should I use a differente value for $resource for each
> core?

If you want different configs for each core, don't use configsets.  Each
core will need its own conf directory with its own config, which can be
different from every other config.

One of the advancements in SolrCloud is the idea of shared configs. 
Every core (shard replica) in a collection pulls exactly the same config
from zookeeper.  That config can be shared between multiple collections
running on multiple servers, so a change in the shared config will
affect all linked collections once they are reloaded.

The configsets feature (which was first available in Solr 4.8) is
intended to bring that same shared configuration to systems NOT running
in cloud mode, but it can only do so for cores on a single machine,
unlike SolrCloud.  By using configsets, you have told Solr that you
*want* the exact same config on multiple cores on that server.

Thanks,
Shawn