# Why the japanese characters(Kanji ) are separated in kibana visualization even though single word and field **URL:** \ **Category:** Kibana\ **Created:** [June 8, 2016, 1:24am UTC](https://discuss.elastic.co/t/why-the-japanese-characters-kanji-are-separated-in-kibana-visualization-even-though-single-word-and-field/52142 "2016-06-08T01:24:19Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![venkat-accel](https://avatars.discourse-cdn.com/v4/letter/v/9f8e36/32.png) [@venkat-accel](https://discuss.elastic.co/u/venkat-accel)\ **Post date:** [June 8, 2016, 1:24am UTC](https://discuss.elastic.co/t/why-the-japanese-characters-kanji-are-separated-in-kibana-visualization-even-though-single-word-and-field/52142/1 "2016-06-08T01:24:19Z")
Hi , I have csv data stored in ES through logstash , currently i able to load the index in Kibana and while display in discovery the data is shown correctly ( word by word in single field) but in the visualization when i added name field as term for aggregation character by character is coming as separate filed. English words are split by each word but japanes words are split by each character or kanji. I want the whole field as single . How can i achieve this. ---
**Author:** ![shaunak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shaunak/32/6643_2.png) [@shaunak](https://discuss.elastic.co/u/shaunak)\ **Post date:** [June 8, 2016, 2:16am UTC](https://discuss.elastic.co/t/why-the-japanese-characters-kanji-are-separated-in-kibana-visualization-even-though-single-word-and-field/52142/2 "2016-06-08T02:16:02Z")
If you are using Logstash to index your data into Elasticsearch, there must be a `.raw` field, corresponding to every `` field in your index. While the string in `` is analyzed by Elasticsearch, the `.raw` field contains the original string in the `` field, as-is, un-analyzed. Try aggregating by this `.raw` field. ---
**Author:** ![venkat-accel](https://avatars.discourse-cdn.com/v4/letter/v/9f8e36/32.png) [@venkat-accel](https://discuss.elastic.co/u/venkat-accel)\ **Post date:** [June 8, 2016, 2:25am UTC](https://discuss.elastic.co/t/why-the-japanese-characters-kanji-are-separated-in-kibana-visualization-even-though-single-word-and-field/52142/3 "2016-06-08T02:25:55Z")
Hi shaunak, Thank you for your quick response . Sorry i did not get any .raw for my current index. is there any setting to get raw field in ES. ---
**Author:** ![venkat-accel](https://avatars.discourse-cdn.com/v4/letter/v/9f8e36/32.png) [@venkat-accel](https://discuss.elastic.co/u/venkat-accel)\ **Post date:** [June 8, 2016, 2:35am UTC](https://discuss.elastic.co/t/why-the-japanese-characters-kanji-are-separated-in-kibana-visualization-even-though-single-word-and-field/52142/4 "2016-06-08T02:35:14Z")
if field name are in japanese can i get .raw ? is there any restrictions for creating field name. ---
**Author:** ![venkat-accel](https://avatars.discourse-cdn.com/v4/letter/v/9f8e36/32.png) [@venkat-accel](https://discuss.elastic.co/u/venkat-accel)\ **Post date:** [June 8, 2016, 2:45am UTC](https://discuss.elastic.co/t/why-the-japanese-characters-kanji-are-separated-in-kibana-visualization-even-though-single-word-and-field/52142/5 "2016-06-08T02:45:00Z")
If i use field names as english fields then problem solved . Thank you for your clue. ## It will be great appreciated if we get raw fields for japanese titles(Field names).. ---
**Author:** ![venkat-accel](https://avatars.discourse-cdn.com/v4/letter/v/9f8e36/32.png) [@venkat-accel](https://discuss.elastic.co/u/venkat-accel)\ **Post date:** [June 8, 2016, 4:34am UTC](https://discuss.elastic.co/t/why-the-japanese-characters-kanji-are-separated-in-kibana-visualization-even-though-single-word-and-field/52142/6 "2016-06-08T04:34:46Z")
raw fileds are creating only if it is default index(logstash.xx.xx.xx) . If we specify index name explicitly then raw fields are not created, so it is not the problem with language. ---
**Author:** ![shaunak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shaunak/32/6643_2.png) [@shaunak](https://discuss.elastic.co/u/shaunak)\ **Post date:** [June 8, 2016, 4:26pm UTC](https://discuss.elastic.co/t/why-the-japanese-characters-kanji-are-separated-in-kibana-visualization-even-though-single-word-and-field/52142/7 "2016-06-08T16:26:21Z")
Hi, that's correct. The `.raw` fields are created if you use the default index in Logstash. The reason for this is that Logstash provides Elasticsearch with an index template with the appropriate mappings for all indices named `logstash-*`. You can see this template here: [https://github.com/logstash-plugins/logstash-output-elasticsearch/blob/master/lib/logstash/outputs/elasticsearch/elasticsearch-template.json](https://github.com/logstash-plugins/logstash-output-elasticsearch/blob/master/lib/logstash/outputs/elasticsearch/elasticsearch-template.json) If you decide to use an index name other than `logstash-*`, this template is not applicable, hence the `.raw` fields are not created automatically. You will need to provide an index template of your own, similar to the one provided by Logstash, matching the name(s) of your indices. You can learn more about index templates in general over here: - [https://www.elastic.co/guide/en/elasticsearch/guide/current/index-templates.html](https://www.elastic.co/guide/en/elasticsearch/guide/current/index-templates.html) - [https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-templates.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-templates.html) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:51pm UTC](https://discuss.elastic.co/t/why-the-japanese-characters-kanji-are-separated-in-kibana-visualization-even-though-single-word-and-field/52142/8 "2017-07-06T13:51:09Z")