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 <apa...@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 >
