You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Kazuaki Hiraga (JIRA)" <ji...@apache.org> on 2019/04/24 09:12:00 UTC
[jira] [Commented] (LUCENE-8777) Inconsistent behavior in
JapaneseTokenizer search mode
[ https://issues.apache.org/jira/browse/LUCENE-8777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16824940#comment-16824940 ]
Kazuaki Hiraga commented on LUCENE-8777:
----------------------------------------
I think the first one is expected behavior from the current user dictionary perspective. If we want to change the behavior, the ticket might mislead the issue. I think it should be *changing behavior of user dictionary*.
> Inconsistent behavior in JapaneseTokenizer search mode
> ------------------------------------------------------
>
> Key: LUCENE-8777
> URL: https://issues.apache.org/jira/browse/LUCENE-8777
> Project: Lucene - Core
> Issue Type: Improvement
> Components: modules/analysis
> Reporter: Tomoko Uchida
> Priority: Minor
>
> A user reported to me about inconsistent behaviour in JapaneseTokenizer's search mode.
> Without user dictionary, JapaneseTokenizer (mode=search) outputs "long token" and all of "short (custom segmented) token"s.
> e.g.:
> 関西国際空港 => 関西 / 関西国際空港 / 国際 / 空港
> With user dictionary, JapaneseTokenizer (mode=search) outputs all short tokens but not long token.
> e.g.:
> {code}
> $ cat config/userdict.txt
> 関西国際空港,関西 国際 空港,カンサイ コクサイ クウコウ,カスタム名詞
> {code}
> 関西国際空港 => 関西 / 国際 / 空港
>
> This behaviour is confusing for users and would be better to be fixed. I am not sure which behaviour is correct, but in my perspective the first one (without user dictionary) is preferable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org