[ 
https://issues.apache.org/jira/browse/SOLR-12655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16576857#comment-16576857
 ] 

Uwe Schindler commented on SOLR-12655:
--------------------------------------

Here is the correct schema.xml addition (same as KoreanAnalyzer defaults from 
Lucene):

{code:xml}
<fieldType name="text_ko" class="solr.TextField" >
  <analyzer>
    <!-- decompoundMode: mixed (is keep original term and add all decompounded 
terms), discard (default, removes the compound form, only keeps the parts), 
none (no decompounding) -->
    <tokenizer class="solr.KoreanTokenizerFactory" decompoundMode="discard" 
outputUnknownUnigrams="false"/>
    <!-- removes some part of speech stuff like EOMI (Pos.E) -->
    <filter class="solr.KoreanPartOfSpeechStopFilterFactory" />
    <!-- Replaces term text with the Hangul transcription of Hanja characters, 
if applicable: -->
    <filter class="solr.KoreanReadingFormFilterFactory" />
    <filter class="solr.LowerCaseFilterFactory" />
  </analyzer>
</fieldType>
{code}

> Add Korean analyzer JAR file (NORI) and schema.xml example to Solr
> ------------------------------------------------------------------
>
>                 Key: SOLR-12655
>                 URL: https://issues.apache.org/jira/browse/SOLR-12655
>             Project: Solr
>          Issue Type: New Feature
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Build, Schema and Analysis
>    Affects Versions: 7.4
>            Reporter: Uwe Schindler
>            Priority: Major
>
> In Lucene 7.4 we added the NORI analyzer for Korean. In contrast to Kuromoji, 
> the JAR file is missing in the distribution (the analyzers-kuromoji is part 
> of main solr distribution). We should also add an updated/new "text_ko" field 
> in the default schema.
> See also SOLR-12255 about the documentation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to