# Kibana parses correctly CSV data file but fails visualization

**URL:** <https://discuss.elastic.co/t/kibana-parses-correctly-csv-data-file-but-fails-visualization/54213>\
**Category:** Kibana\
**Created:** [June 28, 2016, 10:43pm UTC](https://discuss.elastic.co/t/kibana-parses-correctly-csv-data-file-but-fails-visualization/54213 "2016-06-28T22:43:11Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ikovalev](https://avatars.discourse-cdn.com/v4/letter/i/3bc359/32.png) [@ikovalev](https://discuss.elastic.co/u/ikovalev)\
**Post date:** [June 28, 2016, 10:43pm UTC](https://discuss.elastic.co/t/kibana-parses-correctly-csv-data-file-but-fails-visualization/54213/1 "2016-06-28T22:43:11Z")

</div>

Problem with visualization:

1. tokenizes the value of the field. If the field is multi-word, it would create a bar for each work in the field and
2. converts all to lower case

For example, field value like an address "123 Street City" would be represented as 3 bars "123", "street", "city".

---

<div class="post-metadata">

**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 28, 2016, 10:46pm UTC](https://discuss.elastic.co/t/kibana-parses-correctly-csv-data-file-but-fails-visualization/54213/2 "2016-06-28T22:46:31Z")

</div>

This is likely happening because Elasticsearch is [analyzing](https://www.elastic.co/guide/en/elasticsearch/guide/current/analysis-intro.html) your fields. If you want to prevent this, you will need to create a [mapping](https://www.elastic.co/guide/en/elasticsearch/guide/current/mapping-intro.html) for your index(es) and, in that mapping, define the fields to be `not_analyzed`.

---

<div class="post-metadata">

**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 28, 2016, 10:50pm UTC](https://discuss.elastic.co/t/kibana-parses-correctly-csv-data-file-but-fails-visualization/54213/3 "2016-06-28T22:50:12Z")

</div>

BTW, are you using Logstash for parsing the CSV? If so, Logstash will automatically create `.raw` versions of each field that contain the `not_analyzed` values in those fields. So, for example, if you have a field named `column1`, Logstash will also automatically create a field named `column1.raw` for you. If you use the latter field in Kibana, you will get the values as-is, unanalyzed.

---

<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:** [July 6, 2017, 1:48pm UTC](https://discuss.elastic.co/t/kibana-parses-correctly-csv-data-file-but-fails-visualization/54213/4 "2017-07-06T13:48:53Z")

</div>