The SolrServerAdapter warps a Solr CoreContainer and makes it and its cores available as OSGI services so that they can be used with the whiteboard pattern.
Currently when one updates a SolrCore (e.g. registering a core with the same name but a different core directory) with the SolrServerAdapter the old core is removed first and the new one only added later. This means that while on the Solr side both cores could be used simultaneously it is not possible on the OSGI side because of the order of the unregistration and registration.
This issue is about changing this so that on a SolrCore registration of an existing core the workflow is as follows
- update the SolrCore on the CoreContainer
- register the new SolrCore as OSGI service
- unregister the old SolrCore as OSGI service
This issue will also update the FstLinkingEngineComponent so that the initialization can make used of the new Feature. This will avoid any EntityLinking service interruption of the SolrCore used for linking is updated.