Add support for update and removals of SolrCores for Solr servers managed by
Stanbol
------------------------------------------------------------------------------------
Key: STANBOL-375
URL: https://issues.apache.org/jira/browse/STANBOL-375
Project: Stanbol
Issue Type: New Feature
Reporter: Rupert Westenthaler
Assignee: Rupert Westenthaler
Currently the SolrDirectoryManager [1] allows only to create new Solr indexes.
Updates and removals are not supported. This shortcoming also limits the
functionality of the Solr extension to the Sling Installer framework [2] so
that the IndexRemoveTask can not be implemented.
This limitation was mainly because of the fact that changes to CoreContainers
and SolrCores could not be notified to other Components, but with the
completion of STANBOL-354 this is no longer a problem.
Additional Notes:
* The SolrDirectoryManager is currently also useable outside an OSGI
environment. However the here requested functionality heavily depends on OSGI
services. Therefore the solution will be to require OSGI for the new
Implementation and provides a additional implementation that can run outside
OSGI with limited functionality.
* This functionality will me moved from the commons.solr.core bundle to an own
artifact with the name "org.apache.stanbol.commons.solr.managed" and the new
Service will be called ManagedSolrServer. The current component [3] with that
name will be renamed to SolrServerAdapter - because it does not really manage a
SolrServer, but merely adapts the Solr Components to OSGI Components as
descibed by STANBOL-354
[1]
http://svn.apache.org/viewvc/incubator/stanbol/trunk/commons/solr/core/src/main/java/org/apache/stanbol/commons/solr/SolrDirectoryManager.java?revision=1186726&view=markup
[2]
http://svn.apache.org/repos/asf/incubator/stanbol/trunk/commons/solr/install/
[3]
http://svn.apache.org/viewvc/incubator/stanbol/trunk/commons/solr/core/src/main/java/org/apache/stanbol/commons/solr/ManagedSolrServer.java?revision=1195450&view=markup
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
