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

Christian Moen commented on LUCENE-4956:
----------------------------------------

Hello SooMyung,

Thanks for the above regarding field type.  The general approach we have taken 
in Lucene is to do the same analysis at both index and query side.  For 
example, the Japanese analyzer also has functionality to do compound splitting 
and we've discussed doing this one the index side only per default for field 
type {{text_ja}}, but we decided against it.

I've included your field type in the latest code I've checked in just now, but 
it's likely that we will change this in the future.

I'm wondering if you could help me with a few sample sentences that illustrates 
the various options {{KoreanFilter}} has.  I'd like to add some test-cases for 
these to better understand the differences between them and to verify correct 
behaviour.  Test-cases for this is also a useful way to document functionality 
in general.  Thanks for any help with this!
                
> the korean analyzer that has a korean morphological analyzer and dictionaries
> -----------------------------------------------------------------------------
>
>                 Key: LUCENE-4956
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4956
>             Project: Lucene - Core
>          Issue Type: New Feature
>          Components: modules/analysis
>    Affects Versions: 4.2
>            Reporter: SooMyung Lee
>            Assignee: Christian Moen
>              Labels: newbie
>         Attachments: kr.analyzer.4x.tar
>
>
> Korean language has specific characteristic. When developing search service 
> with lucene & solr in korean, there are some problems in searching and 
> indexing. The korean analyer solved the problems with a korean morphological 
> anlyzer. It consists of a korean morphological analyzer, dictionaries, a 
> korean tokenizer and a korean filter. The korean anlyzer is made for lucene 
> and solr. If you develop a search service with lucene in korean, It is the 
> best idea to choose the korean analyzer.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to