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/06/02 23:23:47 UTC
[jira] [Resolved] (STANBOL-208) Add support for "Named Solr
configuration"
[ https://issues.apache.org/jira/browse/STANBOL-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rupert Westenthaler resolved STANBOL-208.
-----------------------------------------
Resolution: Fixed
> Add support for "Named Solr configuration"
> ------------------------------------------
>
> Key: STANBOL-208
> URL: https://issues.apache.org/jira/browse/STANBOL-208
> Project: Stanbol
> Issue Type: New Feature
> Components: Entity Hub
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
> Priority: Minor
>
> The SolrYard already supports to initialise Solr Cores based on the default configuration.
> This default configuration is currently loaded from "solr/core" in the SolrYard bundle.
> The Idea is to extend this by allowing to load "named" Solr Configurations.
> The goal is to use the Stanbol datafileprovider service similar to the
> opennlp.ner engine that also supports to load language specific configurations via the
> classpath if the required files are not present in the datafile directory.
> The used path to load configuration via the classpath will be
> "solr/core/{name}".
> The current default config will be located at "config/solr/core/default" within the SolrYard bundle
> Other generally useful configurations such as
> * index only (no storage of values)
> * entity-tagging (a configuration similar to the index currently used by the autotagger engine)
> should be also included within a Stanbol distribution.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira