You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Antonio David Pérez Morales (JIRA)" <ji...@apache.org> on 2014/08/18 11:31:18 UTC
[jira] [Resolved] (STANBOL-1375) Create Solr Stanbol Camel
Component
[ https://issues.apache.org/jira/browse/STANBOL-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antonio David Pérez Morales resolved STANBOL-1375.
--------------------------------------------------
Resolution: Fixed
StanbolSolrComponent has been developed with the next features:
- Scheme used by default: stanbol-solr
- The scheme can be configured through the Felix console
- Parameters allowed:
- ldpath: Contains the LDPath to be used to retrieve the properties from entities to be indexed in Solr
- fields: comma-separated list of field names to be extracted from entities
- useDereferenceLdpath: if no ldpath parameter is defined, it determines if we need to use the ldpath program configured in the dereference engine or the ldpath program provided through a request parameter (enhancer.engines.dereference.ldpath)
Example: from(direct://test).to(chain://default).to(stanbol-solr://localhost:8983/solr/collection1)
> Create Solr Stanbol Camel Component
> -----------------------------------
>
> Key: STANBOL-1375
> URL: https://issues.apache.org/jira/browse/STANBOL-1375
> Project: Stanbol
> Issue Type: Sub-task
> Components: Enhancer
> Reporter: Rafa Haro
> Assignee: Antonio David Pérez Morales
> Fix For: 1.0.0
>
>
> Create Solr Stanbol Camel component, for allowing routing Solr within routes in Stanbol (also scheme configurable through OSGI console).
> The Solr Component should convert ContentItem metadata into configured solr fields. LDPath fields and plain entities' properties in the Enhancement Structure can be configured to be extracted
--
This message was sent by Atlassian JIRA
(v6.2#6252)