-
Notifications
You must be signed in to change notification settings - Fork 3
Description
In our coli-conc-server ecosystem, after the last deployment—which included an updated schema.xml—documents were indexed correctly, but the active configuration still reflected the previous schema. Specifically, on the server the directory
$DATA/solr_data/terminologies/
did not contain the most recent version of schema.xml. This mismatch creates discrepancies between the “source” configuration in our ConfigSet and the schema actually in use by the Solr core.
Proposed Solution (revised):
Refactor the core-creation/reload process within the bartoc-search SolrClient module to:
- Load the ConfigSet directory in code (e.g. read
server/solr/configsets/terminologies/conf/); - Push each config file directly via HTTP from Node—using the Solr ConfigSets API
- Trigger a reload of the
terminologiescore/collection immediately after uploading all files:
something like
GET /solr/admin/cores?action=RELOAD&core=terminologies
This approach centralizes all ConfigSet management in the SolrClient module without the need to manage artifacts in Docker or in multiple repositories.
- ConfigSets documentation: https://solr.apache.org/guide/configsets.html
- CoreAdmin API guide: https://solr.apache.org/guide/coreadmin-api.html