the korean analyzer that has a korean morphological analyzer and dictionaries [LUCENE-4956]

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.

---
Migrated from [LUCENE-4956](https://issues.apache.org/jira/browse/LUCENE-4956) by SooMyung Lee, 4 votes, updated Feb 09 2014
Attachments: [eval.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-4956/eval.patch), [kr.analyzer.4x.tar](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-4956/kr.analyzer.4x.tar), [lucene4956.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-4956/lucene4956.patch), [lucene-4956.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-4956/lucene-4956.patch), [LUCENE-4956.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-4956/LUCENE-4956.patch)

Start by reviewing the migrated LUCENE-4956 discussion and the attached eval.patch, lucene4956.patch, and Korean analyzer archive. Determine the current Lucene and Solr integration requirements from that material; done means the proposed Korean morphological analyzer, tokenizer, filter, and dictionaries are sufficiently specified and accepted for the project.

Written by the indexing model from the issue text.