: Yes I was thinking the same thing, although I was hoping there was a
: more elegant mechanism exposed by the solr infrastructure code to handle
: the shared map, aside from just using a global that is.
a) if you have a large data structure you wnat to share between SolrCores,
you might be able to find a place to register that with the CoreContainer
i'd have to look at the API a bit more to think about wether anything
like that exists.
b) at a minimum you could create a special SolrCore with a special name,
and your plugin (in any core) could know that if the current core has
the special name, construct the data - else: ask the CoreContainer for
that special SolrCor by name, and then as that special SolrCore for it's
instance of
the same plugin and refrence the data from there.
C) ...
: > We have a multi-core set up with a fairly large synonym file, all
: > cores share the same schema.xml and synonym file but when solr loads
: > the cores, it loads multiple instances of the synonym map, this is a
If all of your cores use an identical schema.xml file, you should try
using the "shareSchema" option of <cores/> in solr.xml...
https://wiki.apache.org/solr/CoreAdmin#cores
...if the file path for the schema.xml is the same for multiple cores,
then only one instance of the IndexSchema (and FieldTYpes, and Analyzers,
... and SynonymMaps) should be constructed from the schema.xml for all of
those cores.
It doesn't help you if you have *differnet* schema.xml files that share a
single set of synonyms, but should be exactly what you want for the
usecase of many cores with identical schema.xml files
(disclaimer: i have not personally used/relied-on shareSchema="true" -
there may be caveats/bugs i'm not aware of)
-Hoss
