lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (Commented) (JIRA) <>
Subject [jira] [Commented] (LUCENE-3909) Move Kuromoji to analysis.ja and introduce Japanese* naming
Date Sun, 25 Mar 2012 13:43:28 GMT


Jan Høydahl commented on LUCENE-3909:

> Move Kuromoji to analysis.ja and introduce Japanese* naming
> -----------------------------------------------------------
>                 Key: LUCENE-3909
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: modules/analysis
>    Affects Versions: 3.6, 4.0
>            Reporter: Christian Moen
>            Assignee: Christian Moen
> Lucene/Solr 3.6 and 4.0 will get out-of-the-box Japanese language support through {{KuromojiAnalyzer}},
{{KuromojiTokenizer}} and various other filters.  These filters currently live in {{org.apache.lucene.analysis.kuromoji}}.
> I'm proposing that we move Kuromoji to a new Japanese package {{org.apache.lucene.analysis.ja}}
in line with how other languages are organized.  As part of this, I also think we should rename
{{KuromojiAnalyzer}} to {{JapaneseAnalyzer}}, etc. to further align naming to our conventions
by making it very clear that these analyzers are for Japanese.  (As much as I like the name
"Kuromoji", I think "Japanese" is more fitting.)
> A potential issue I see with this that I'd like to raise and get feedback on, is that
end-users in Japan and elsewhere who use lucene-gosen could have issues after an upgrade since
lucene-gosen is in fact releasing its analyzers under the {{org.apache.lucene.analysis.ja}}
namespace (and we'd have a name clash).
> I believe users should have the freedom to choose whichever Japanese analyzer, filter,
etc. they'd like to use, and I don't want to propose a name change that just creates unnecessary
problems for users, but I think the naming proposed above is most fitting for a Lucene/Solr

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message