[
https://issues.apache.org/jira/browse/STANBOL-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rupert Westenthaler resolved STANBOL-1440.
------------------------------------------
Resolution: Fixed
implemented with http://svn.apache.org/r1701226 in 0.12 and
http://svn.apache.org/r1701228 in trunk
> Support SolrCore swap like feature
> ----------------------------------
>
> Key: STANBOL-1440
> URL: https://issues.apache.org/jira/browse/STANBOL-1440
> Project: Stanbol
> Issue Type: Improvement
> Components: Commons, Enhancement Engines
> Affects Versions: 0.12.0
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
> Priority: Minor
> Fix For: 1.0.0, 0.12.1
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
