Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
7.4
-
None
-
None
-
Elasticsearch version: Version: Version: 6.4.2, Build: default/tar/04711c2/2018-09-26T13:34:09.098244Z, JVM: 1.8.0_131
Plugins installed: [analysis-nori]
JVM version:
java version "1.8.0_131"
Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)OS version: Darwin Kijuui-MacBook-Pro.local 17.7.0 Darwin Kernel Version 17.7.0: Thu Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~1/RELEASE_X86_64 x86_64
Elasticsearch version: Version: Version: 6.4.2, Build: default/tar/04711c2/2018-09-26T13:34:09.098244Z, JVM: 1.8.0_131 Plugins installed: [analysis-nori] JVM version: java version "1.8.0_131" Java(TM) SE Runtime Environment (build 1.8.0_131-b11) Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode) OS version: Darwin Kijuui-MacBook-Pro.local 17.7.0 Darwin Kernel Version 17.7.0: Thu Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~1/RELEASE_X86_64 x86_64
-
New, Patch Available
Description
We can reproduce it from Elasticsearch.
When we run the following command:
GET _analyze
{
"analyzer": "nori",
"text": "공단시"
}
It returns the following as expected:
{
"tokens": [
,
]
}
But if we run with "공단시 " (with a trailing space)
GET _analyze
{ "analyzer": "nori", "text": "공단시 " }It returns
{
"tokens": [
,
]
}
The second token should be "시" instead of "씨".