Closed asfimport closed 12 years ago
Michael McCandless (@mikemccand) (migrated from JIRA)
+1
Robert Muir (@rmuir) (migrated from JIRA)
+1
Christian Moen (@cmoen) (migrated from JIRA)
Thanks, Robert and Mike.
It would be great to get your feedback on this as well, Koji.
Jan Høydahl (@janhoy) (migrated from JIRA)
+1
Koji Sekiguchi (@kojisekig) (migrated from JIRA)
Hi Christian, please go.
Christian Moen (@cmoen) (migrated from JIRA)
Committed revision 1305297 to trunk
. Backporting to branch_3x
.
Christian Moen (@cmoen) (migrated from JIRA)
Committed revision 1305367 and 1305372 on branch_3x
.
I forgot to rename a few Solr test classes. Will follow up now in this JIRA.
Christian Moen (@cmoen) (migrated from JIRA)
Committed revision 1305421 on trunk
and 1305437 to branch_3x
.
Christian Moen (@cmoen) (migrated from JIRA)
The move is done.
Many thanks to Uwe for pointing out a Java 5 breakage I did – and to Robert for fixing it very quickly in revision 1305452 on branch_3x
.
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 inorg.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 renameKuromojiAnalyzer
toJapaneseAnalyzer
, 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 release.
Migrated from LUCENE-3909 by Christian Moen (@cmoen), resolved Mar 26 2012