[
https://issues.apache.org/jira/browse/LUCENE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-1817:
------------------------------------
Attachment: LUCENE-1817-mark-cn-experimental.patch
We should mark the smartcn module experimental as we plan to do heavy
refactoring after 2.9 is out. This patch adds a notice to package.html and
JavaDoc.
Quoting Mark Miller from the list:
bq. Warning users that you don't plan on promising back compat with
experimental warnings seems like a good idea to me.
> it is impossible to use a custom dictionary for SmartChineseAnalyzer
> --------------------------------------------------------------------
>
> Key: LUCENE-1817
> URL: https://issues.apache.org/jira/browse/LUCENE-1817
> Project: Lucene - Java
> Issue Type: Bug
> Components: contrib/analyzers
> Reporter: Robert Muir
> Priority: Minor
> Attachments: LUCENE-1817-mark-cn-experimental.patch
>
>
> it is not possible to use a custom dictionary, even though there is a lot of
> code and javadocs to allow this.
> This is because the custom dictionary is only loaded if it cannot load the
> built-in one (which is of course, in the jar file and should load)
> {code}
> public synchronized static WordDictionary getInstance() {
> if (singleInstance == null) {
> singleInstance = new WordDictionary(); // load from jar file
> try {
> singleInstance.load();
> } catch (IOException e) { // loading from jar file must fail before it
> checks the AnalyzerProfile (where this can be configured)
> String wordDictRoot = AnalyzerProfile.ANALYSIS_DATA_DIR;
> singleInstance.load(wordDictRoot);
> } catch (ClassNotFoundException e) {
> throw new RuntimeException(e);
> }
> }
> return singleInstance;
> }
> {code}
> I think we should either correct this, document this, or disable custom
> dictionary support...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
