You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Rupert Westenthaler (JIRA)" <ji...@apache.org> on 2011/03/25 06:35:05 UTC
[jira] [Resolved] (STANBOL-118) Refactor the functionality to
manage a Solr directory out of the EmbeddedSolrProvider
[ https://issues.apache.org/jira/browse/STANBOL-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rupert Westenthaler resolved STANBOL-118.
-----------------------------------------
Resolution: Fixed
Resolved with #1085255:
see the new SolrDirectoryManager
> Refactor the functionality to manage a Solr directory out of the EmbeddedSolrProvider
> -------------------------------------------------------------------------------------
>
> Key: STANBOL-118
> URL: https://issues.apache.org/jira/browse/STANBOL-118
> Project: Stanbol
> Issue Type: Improvement
> Components: Entity Hub
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
>
> Currently the EmbeddedSolrProvider is used for two thinks:
> (1) to correctly initialize SolrServer instances for Index locations referring to a directory on the local file stystem
> (2) managing and (on demand) initialization of new (empty) indexes within a configurable directory that in managed for the SolrYard.
> The goal is to define an own service that covers (2). The SorYard would than directly define a dependency on this Service and not implicitly relay that the EmbeddedSolrProvider provides this functionality.
> In addition this will resolve STANBOL-117 because the EmbeddedSolrProvider would no longer require any configuration (see comment Rupert Westenthaler 21/Mar/11 14:49 for details)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira