# Not\_Analyzed Field Splits On Spaces

**URL:** <https://discuss.elastic.co/t/not-analyzed-field-splits-on-spaces/33825>\
**Category:** Kibana\
**Created:** [November 5, 2015, 3:45am UTC](https://discuss.elastic.co/t/not-analyzed-field-splits-on-spaces/33825 "2015-11-05T03:45:53Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![gromit](https://avatars.discourse-cdn.com/v4/letter/g/ac8455/32.png) [@gromit](https://discuss.elastic.co/u/gromit)\
**Post date:** [November 5, 2015, 3:45am UTC](https://discuss.elastic.co/t/not-analyzed-field-splits-on-spaces/33825/1 "2015-11-05T03:45:53Z")

</div>

I have a field marked as type string, not\_analyzed. When visualising data from this field each word is separated.  
It is as if the field were mapped as analyzed.  
I have another index which has the same field not\_analyzed and visualisation does not separate the words in the string.  
Perhaps a bug?

---

<div class="post-metadata">

**Author:** ![tbragin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tbragin/32/45166_2.png) [@tbragin](https://discuss.elastic.co/u/tbragin)\
**Post date:** [November 5, 2015, 5:06am UTC](https://discuss.elastic.co/t/not-analyzed-field-splits-on-spaces/33825/2 "2015-11-05T05:06:30Z")

</div>

May need more details here. Could you post the mapping in ES and a screenshot of how you are creating the visualization?

---

<div class="post-metadata">

**Author:** ![gromit](https://avatars.discourse-cdn.com/v4/letter/g/ac8455/32.png) [@gromit](https://discuss.elastic.co/u/gromit)\
**Post date:** [November 5, 2015, 5:18am UTC](https://discuss.elastic.co/t/not-analyzed-field-splits-on-spaces/33825/3 "2015-11-05T05:18:35Z")

</div>

Just a simple mapping:  
(extract)  
},  
"source\_name" : {  
"index" : "not\_analyzed",  
"type" : "string"  
}

With the visualisation it is just a basic pie or bar chart.  
So, with a bar chart using the timestamp for X-Axis and a Split Bar Sub Aggregation using terms and them 'source\_name' field for example.  
If the value of the source\_name field is "my own application" then the bar will be split into my, own and application.  
The same with a pie chart. It's as if the field is mapped as analyzed.

---

<div class="post-metadata">

**Author:** ![tbragin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tbragin/32/45166_2.png) [@tbragin](https://discuss.elastic.co/u/tbragin)\
**Post date:** [November 5, 2015, 5:24am UTC](https://discuss.elastic.co/t/not-analyzed-field-splits-on-spaces/33825/4 "2015-11-05T05:24:34Z")

</div>

I've not seen that happen. And you say you have another index where this works as expected? Any errors on the Elasticsearch side?

---

<div class="post-metadata">

**Author:** ![kmmats](https://avatars.discourse-cdn.com/v4/letter/k/43a26b/32.png) [@kmmats](https://discuss.elastic.co/u/kmmats)\
**Post date:** [March 2, 2016, 1:28am UTC](https://discuss.elastic.co/t/not-analyzed-field-splits-on-spaces/33825/5 "2016-03-02T01:28:01Z")

</div>

I'm seeing this issue as well. In my case it also extends to the queries being run directly on elasticsearch. In my example it's a field being generated from 3 copy\_to statements

```
        "field_1": {
            "type": "string",
            "fields": {
              "raw": {
                "ignore_above": 256,
                "index": "not_analyzed",
                "type": "string"
              }},
            "copy_to": "field_123"
        }, 
        "field_2": {
            "type": "string",
            "fields": {
              "raw": {
                "ignore_above": 256,
                "index": "not_analyzed",
                "type": "string"
              }},
            "copy_to": "field_123"
        }, 
        "field_3": {
            "type": "string",
            "fields": {
              "raw": {
                "ignore_above": 256,
                "index": "not_analyzed",
                "type": "string"
              }},
            "copy_to": "field_123"
        },
        "field_123" :{
            "type": "string",
            "index": "not_analyzed"
        }
```

---

<div class="post-metadata">

**Author:** ![dkota](https://avatars.discourse-cdn.com/v4/letter/d/46a35a/32.png) [@dkota](https://discuss.elastic.co/u/dkota)\
**Post date:** [June 21, 2016, 4:59pm UTC](https://discuss.elastic.co/t/not-analyzed-field-splits-on-spaces/33825/6 "2016-06-21T16:59:38Z")

</div>

I'm seeing this issue. Have you found a solution to this?

---

<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:49pm UTC](https://discuss.elastic.co/t/not-analyzed-field-splits-on-spaces/33825/7 "2017-07-06T13:49:42Z")

</div>