Resource Loading
Solr components can be configured using resources: data stored in external files that may be referred to in a location-independent fashion.
Examples of resources include: files needed by schema components, e.g., a stopword list for Stop Filter; and machine-learned models for Learning To Rank. Resources are typically resolved from the configSet but there are other options too.
Solr’s resources are generally only loaded initially when the Solr collection or Solr core is loaded. After you update a resource, you’ll typically need to reload the affected collections when running SolrCloud, or the cores when running a user-managed cluster or single-node installation. Restarting all affected Solr nodes also works. Managed Resources can be manipulated via APIs and do not need an explicit reload.
Resources in Configsets
Configsets are the directories containing solrconfig.xml
, the schema, and resources referenced by them.
In SolrCloud they are stored in ZooKeeper.
In a user-managed cluster and a single-node installation they are stored on the file system.
In any mode, resources may be shared or may be dedicated to a configSet.
Prefer to put resources here.