[
https://issues.apache.org/jira/browse/LUCENE-6837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15093057#comment-15093057
]
Ippei UKAI edited comment on LUCENE-6837 at 1/12/16 1:15 AM:
-------------------------------------------------------------
I wanted to give this feature a try, and would like to share what I did so you
can try it too.
Attached is a slightly modified version of JapaneseTokenizer from r1717713
compiled for use with Lucene/Solr 5.4. Basically, modified classes are in a
separate package so it does not conflict with existing.
solrconfig.xml:
{code:xml}
<lib dir="${solr.solr.home}/lib/LUCENE-6837" /> }}
{code}
(if you place the files under $SOLR_HOME/lib/LUCENE-6837)
schema.xml:
{code:xml}
<tokenizer
class="org.apache.lucene.analysis.ja6837.JapaneseTokenizerFactory"
mode="NORMAL"
discardPunctuation="true"
nBestExamples="/シニアソフトウェアエンジニア-ソフトウェア/数学部長谷川-長谷川/"
/>
{code}
was (Author: ippei):
I wanted to give this feature a try, and would like to share what I did so you
can try it too.
Attached is a slightly modified version of JapaneseTokenizer from r1717713
compiled for use with Lucene/Solr 5.4. Basically, modified classes are in a
separate package so it does not conflict with existing.
solrconfig.xml:
<lib dir="${solr.solr.home}/lib/LUCENE-6837" />
(if you place the files under $SOLR_HOME/lib/LUCENE-6837)
schema.xml:
<tokenizer
class="org.apache.lucene.analysis.ja6837.JapaneseTokenizerFactory"
mode="NORMAL"
discardPunctuation="true"
nBestExamples="/シニアソフトウェアエンジニア-ソフトウェア/数学部長谷川-長谷川/"
/>
> Add N-best output capability to JapaneseTokenizer
> -------------------------------------------------
>
> Key: LUCENE-6837
> URL: https://issues.apache.org/jira/browse/LUCENE-6837
> Project: Lucene - Core
> Issue Type: Improvement
> Components: modules/analysis
> Affects Versions: 5.3
> Reporter: KONNO, Hiroharu
> Assignee: Christian Moen
> Priority: Minor
> Attachments: LUCENE-6837 for 5.4.zip, LUCENE-6837.patch,
> LUCENE-6837.patch, LUCENE-6837.patch, LUCENE-6837.patch, LUCENE-6837.patch
>
>
> Japanese morphological analyzers often generate mis-segmented tokens. N-best
> output reduces the impact of mis-segmentation on search result. N-best output
> is more meaningful than character N-gram, and it increases hit count too.
> If you use N-best output, you can get decompounded tokens (ex:
> "シニアソフトウェアエンジニア" => {"シニア", "シニアソフトウェアエンジニア", "ソフトウェア", "エンジニア"}) and
> overwrapped tokens (ex: "数学部長谷川" => {"数学", "部", "部長", "長谷川", "谷川"}),
> depending on the dictionary and N-best parameter settings.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
