# Field set as not analyzed but kibana shows it as analyzed

**URL:** https://discuss.elastic.co/t/field-set-as-not-analyzed-but-kibana-shows-it-as-analyzed/33450
**Category:** Elasticsearch
**Created:** [November 1, 2015, 12:50am UTC](https://discuss.elastic.co/t/field-set-as-not-analyzed-but-kibana-shows-it-as-analyzed/33450 "2015-11-01T00:50:24Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![prtkgaur](https://avatars.discourse-cdn.com/v4/letter/p/e36b37/32.png) [@prtkgaur](https://discuss.elastic.co/u/prtkgaur)
#### Post date: [November 1, 2015, 12:50am UTC](https://discuss.elastic.co/t/field-set-as-not-analyzed-but-kibana-shows-it-as-analyzed/33450/1 "2015-11-01T00:50:24Z")

</div>

Index template :

```
{
  "template" : "index-*",
  "settings" : {
    "index.refresh_interval" : "10s"
  },
  "mappings" : {
    "_default_" : {
       "_all" : {"enabled" : true},
       "dynamic_templates" : [ {
         "string_fields" : {
           "match" : "*",
           "match_mapping_type" : "string",
           "mapping" : { "type" : "string", "index" : "analyzed", "omit_norms" : true }
         }
       } ],
       "properties" : {
         "@version": { "type": "string", "index": "not_analyzed" },
         "attribute_map.Machine": { "type": "string", "index": "not_analyzed" },
         "attribute_map.Service": { "type": "string", "index": "not_analyzed" },
         "attribute_map.Task": { "type": "string", "index": "not_analyzed" },
         "guid": { "type": "string", "index": "not_analyzed" },
         "system_info.cluster_id": { "type": "string", "index": "not_analyzed" },
         "system_info.cluster_name": { "type": "string", "index": "not_analyzed" },
         "system_info.release_name": { "type": "string", "index": "not_analyzed" },
         "geoip" : {
           "type" : "object",
             "dynamic": true,
             "path": "full",
             "properties" : {
               "location" : { "type" : "geo_point" }
             }
         }
       }
    }
  }
}

```

But kibana is showing fields such as system\_info.cluster\_name as analyzed. Am I missing any step here?

![](https://us1.discourse-cdn.com/elastic/original/2X/5/5bc1dea932b0c5402163380a4617923ed14f4145.png)

1. As some data already existed in the system.
2. I delete all the indices
3. Updated the mapping
4. Repushed the data  
( BTW is deleting old data necessary for the new mapping to take effect? )

---

<div class="post-metadata">

### Author: ![prtkgaur](https://avatars.discourse-cdn.com/v4/letter/p/e36b37/32.png) [@prtkgaur](https://discuss.elastic.co/u/prtkgaur)
#### Post date: [November 2, 2015, 4:13am UTC](https://discuss.elastic.co/t/field-set-as-not-analyzed-but-kibana-shows-it-as-analyzed/33450/2 "2015-11-02T04:13:44Z")

</div>

Hi guys any update on this?

---

<div class="post-metadata">

### Author: ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [November 2, 2015, 7:06am UTC](https://discuss.elastic.co/t/field-set-as-not-analyzed-but-kibana-shows-it-as-analyzed/33450/3 "2015-11-02T07:06:42Z")

</div>

First of all, is system\_info.cluster\_id supposed to be a single field,

```
"system_info.cluster_id": "some value"

```

or a nested field:

```
"system_info": {
  "cluster_id": "some value",
  ...
}

```

In the former case you should reconsider since fields with dots aren't supported in ES 2.0. In the latter case you have the wrong syntax in your index template. Following the pattern of the geoip field.

General advice for index templates:

- Have you verified that your index template has been picked up by ES (e.g. by using the get index template API)?
- Have you verified with the get mapping API that the recreated index has the wrong mapping (i.e. that it's not something on the Kibana side that's wrong)?
- Have you verified that there aren't any other index templates also matching index-\* indexes?

> BTW is deleting old data necessary for the new mapping to take effect?

You can't change existing mappings so an index needs to be recreated for new mappings to take effect.

> Hi guys any update on this?

Please refrain from thread-bumping at least during weekends.

---

<div class="post-metadata">

### Author: ![prtkgaur](https://avatars.discourse-cdn.com/v4/letter/p/e36b37/32.png) [@prtkgaur](https://discuss.elastic.co/u/prtkgaur)
#### Post date: [November 2, 2015, 9:16pm UTC](https://discuss.elastic.co/t/field-set-as-not-analyzed-but-kibana-shows-it-as-analyzed/33450/4 "2015-11-02T21:16:09Z")

</div>

Thanks a lot Magnus. Yes it was a json field and i was assuming that the filed name was dot separated.

My bad shouldn't have done thread bumping over the weekend.

---

<div class="post-metadata">

### Author: ![sidjain2485](https://avatars.discourse-cdn.com/v4/letter/s/e19adc/32.png) [@sidjain2485](https://discuss.elastic.co/u/sidjain2485)
#### Post date: [March 9, 2016, 6:02am UTC](https://discuss.elastic.co/t/field-set-as-not-analyzed-but-kibana-shows-it-as-analyzed/33450/5 "2016-03-09T06:02:35Z")

</div>

@prtkgaur same issue with me.Could you please let me know how have you sorted it out ?

---

<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 5, 2017, 11:10pm UTC](https://discuss.elastic.co/t/field-set-as-not-analyzed-but-kibana-shows-it-as-analyzed/33450/6 "2017-07-05T23:10:03Z")

</div>