You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Dawid Weiss (JIRA)" <ji...@apache.org> on 2015/10/08 09:48:27 UTC
[jira] [Updated] (LUCENE-6775) Improve MorfologikFilterFactory to
allow arbitrary dictionaries from ResourceLoader
[ https://issues.apache.org/jira/browse/LUCENE-6775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dawid Weiss updated LUCENE-6775:
--------------------------------
Fix Version/s: (was: 5.4)
(was: Trunk)
> Improve MorfologikFilterFactory to allow arbitrary dictionaries from ResourceLoader
> -----------------------------------------------------------------------------------
>
> Key: LUCENE-6775
> URL: https://issues.apache.org/jira/browse/LUCENE-6775
> Project: Lucene - Core
> Issue Type: Improvement
> Components: modules/analysis
> Reporter: Uwe Schindler
> Assignee: Uwe Schindler
> Attachments: LUCENE-6775.patch, LUCENE-6775.patch, LUCENE-6775.patch
>
>
> Followup issue for LUCENE-6774: The filter ctor already allows to pass any dictionary to the filter, but you have no chance to configure this through the Factory (CustomAnalyzer/Solr/Elasticsearch/...). This will add 2 parameters to the factory (exclusive with the dictionary string specifying language, default "pl"), to load FSA (dictionary) and corresponding property file (metadata/featureData). This dictionary could be placed, e.g. in Solr's conf dir and loaded, because this would be done via ResourceLoader.
> Alternatively the language could still be passed, but must be part of JAR file distribution. Currently this defaults to "pl" at the moment and plain Lucene does not allow more, unless you add own JAR files. So practically, the parameter is useless for a pure, uncustomized Lucene-Impl.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org