[
https://issues.apache.org/jira/browse/LUCENE-6775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14737641#comment-14737641
]
ASF subversion and git services commented on LUCENE-6775:
---------------------------------------------------------
Commit 1702118 from [~thetaphi] in branch 'dev/trunk'
[ https://svn.apache.org/r1702118 ]
LUCENE-6775: Improved MorfologikFilterFactory to allow loading of custom
dictionaries from ResourceLoader
> 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
> Fix For: Trunk, 5.4
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
