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 2013/12/17 21:16:07 UTC
[jira] [Resolved] (STANBOL-1242) Lucene FST linking engine should
be registered even if no FST models are present
[ https://issues.apache.org/jira/browse/STANBOL-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rupert Westenthaler resolved STANBOL-1242.
------------------------------------------
Resolution: Fixed
fixed
with http://svn.apache.org/r1551671 in the 0.12 branch
with http://svn.apache.org/r1551673 in the trunk
> Lucene FST linking engine should be registered even if no FST models are present
> --------------------------------------------------------------------------------
>
> Key: STANBOL-1242
> URL: https://issues.apache.org/jira/browse/STANBOL-1242
> Project: Stanbol
> Issue Type: Improvement
> Components: Enhancement Engines
> Affects Versions: 0.12.0
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
>
> Currently an Exception is thrown if no FST model was found for the configured values. This should be changed to a warning. In addition the Engine should be registered but will be inactive (return CANNOT_ENHANCE for all content items).
> The main reasons for this change is that an empty vocabulary (e.g of a newly created ManagedSite) would automatically cause the Component to go into the unsatisfied state
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)