# Issue with the example from the ES blog

**URL:** https://discuss.elastic.co/t/issue-with-the-example-from-the-es-blog/354000
**Category:** Elasticsearch
**Created:** [February 23, 2024, 3:57pm UTC](https://discuss.elastic.co/t/issue-with-the-example-from-the-es-blog/354000 "2024-02-23T15:57:20Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![profuel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/profuel/32/132041_2.png) [@profuel](https://discuss.elastic.co/u/profuel)
#### Post date: [February 23, 2024, 3:57pm UTC](https://discuss.elastic.co/t/issue-with-the-example-from-the-es-blog/354000/1 "2024-02-23T15:57:20Z")

</div>

Hi there!  
I'm trying to setup a proper search for the Japanese audience.  
I found this blog post - [How to implement Japanese full-text search in Elasticsearch | Elastic Blog](https://www.elastic.co/blog/how-to-implement-japanese-full-text-search-in-elasticsearch), though the example here is not accepted neither by 7.7 (on AWS OpenSearch) nor by 7.10.1 (local env .

Error message:

```auto
term: 東京大学 analyzed to a token (東京大学) with position increment != 1 (got: 0)

```

If I run analyser on the same index without synonyms  
{  
"analyzer" : "ja\_kuromoji\_index\_analyzer",  
"text" : "東京大学"  
}  
, I get:

```auto
{ 
"tokens": [ 
{ 
"token": "東京",
"start_offset": 0,
"end_offset": 2,
"type": "word",
"position": 0
},
{ 
"token": "東京大学",
"start_offset": 0,
"end_offset": 4,
"type": "word",
"position": 0,
"positionLength": 2
},
{ 
"token": "大学",
"start_offset": 2,
"end_offset": 4,
"type": "word",
"position": 1
}
]
}

```

Language-wise, this synonym makes total sense:  
東京 - Tokyo  
大学 - University  
東京大学 - University of Tokyo  
東大 - name of the university of Tokyo

The only working solution is synonym:  
"東京 大学 =\> 東大" (with a space between words)  
Though it doesn't work as expected.

Is there any chance to make it work?  
Do I miss some tokenizer/analyzer magic internal logic?

Thanks!

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 23, 2024, 3:57pm UTC](https://discuss.elastic.co/t/issue-with-the-example-from-the-es-blog/354000/2 "2024-02-23T15:57:20Z")

</div>

OpenSearch/OpenDistro are AWS run products and differ from the original Elasticsearch and Kibana products that Elastic builds and maintains. You may need to contact them directly for further assistance.

(This is an automated response from your friendly Elastic bot. Please report this post if you have any suggestions or concerns :elasticheart: )

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 22, 2024, 3:57pm UTC](https://discuss.elastic.co/t/issue-with-the-example-from-the-es-blog/354000/3 "2024-03-22T15:57:55Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
