# Field type conflict

**URL:** https://discuss.elastic.co/t/field-type-conflict/56686
**Category:** Kibana
**Created:** [July 29, 2016, 12:03am UTC](https://discuss.elastic.co/t/field-type-conflict/56686 "2016-07-29T00:03:22Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![stecino](https://avatars.discourse-cdn.com/v4/letter/s/ea666f/32.png) [@stecino](https://discuss.elastic.co/u/stecino)
#### Post date: [July 29, 2016, 12:03am UTC](https://discuss.elastic.co/t/field-type-conflict/56686/1 "2016-07-29T00:03:22Z")

</div>

In my filter I am converting field values for response and response\_time from string to integer and float respectively.

In my mapping template I have the following snippet:

```
   "mappings": {
        "_default_": {
            "dynamic_templates": [
               {
                    "string": {
                        "mapping": {
                            "index": "not_analyzed",
                            "type": "number"
                        },
                        "match": "response*"
                    }
                }
            ]
        }
    }

```

when I get the mapping for my index I get:

curl -XGET localhost:9200/blah/\_mapping?pretty  
{  
"blah" : {  
"mappings" : {  
"_default_" : {  
"dynamic\_templates" : [ {  
"string" : {  
"mapping" : {  
"index" : "not\_analyzed",  
"type" : "string"  
},  
"match" : "cookie"  
}  
}, {  
"string" : {  
"mapping" : {  
"index" : "not\_analyzed",  
"type" : "string"  
},  
"match" : "httpversion"  
}  
}, {  
"string" : {  
"mapping" : {  
"index" : "not\_analyzed",  
"type" : "number"  
},  
"match" : "response\*"  
}  
}, {  
"string" : {  
"mapping" : {  
"index" : "not\_analyzed",  
"type" : "string"  
},  
"match" : "remote\_addr"  
}  
} ]  
},  
"nginx" : {  
"dynamic\_templates" : [  
}, **{**  
\*\* "string" : {\*\*  
\*\* "mapping" : {\*\*  
\*\* "index" : "not\_analyzed",\*\*  
\*\* "type" : "number"\*\*  
\*\* },\*\*  
\*\* "match" : "response\*"\*\*  
\*\* }\*\*  
\*\* },\*\* {  
"string" : {  
"mapping" : {  
"index" : "not\_analyzed",  
"type" : "string"  
},  
"match" : "remote\_addr"  
}  
} ],  
"properties" : {  
"@timestamp" : {  
"type" : "date",  
"format" : "strict\_date\_optional\_time||epoch\_millis"  
},  
"@version" : {  
"type" : "string"  
},  
"agent" : {  
"type" : "string"  
},  
"bytes" : {  
"type" : "string"  
},  
"cookie" : {  
"type" : "string"  
},  
"http\_x\_forwarded\_for" : {  
"type" : "string",  
"index" : "not\_analyzed"  
},  
"http\_x\_forwarded\_for1" : {  
"type" : "string"  
},  
"http\_x\_forwarded\_for2" : {  
"type" : "string"  
},  
"httpversion" : {  
"type" : "string"  
},  
"input\_type" : {  
"type" : "string"  
},  
"kafka" : {  
"properties" : {  
"consumer\_group" : {  
"type" : "string"  
},  
"msg\_size" : {  
"type" : "long"  
},  
"partition" : {  
"type" : "long"  
},  
"topic" : {  
"type" : "string"  
}  
}  
},  
"nginx\_host" : {  
"type" : "string",  
"index" : "not\_analyzed"  
},  
"offset" : {  
"type" : "long"  
},  
"platform" : {  
"type" : "string"  
},  
"referrer" : {  
"type" : "string"  
},  
"remote\_addr" : {  
"type" : "string",  
"index" : "not\_analyzed"  
},  
"request" : {  
"type" : "string"  
},  
**"response" : {**  
\*\* "type" : "long"\*\*  
\*\* },\*\*  
\*\* "response\_time" : {\*\*  
\*\* "type" : "double"\*\*  
\*\* },\*\*  
"source" : {  
"type" : "string",  
"index" : "not\_analyzed"  
},  
"tags" : {  
"type" : "string"  
},  
"timestamp" : {  
"type" : "string"  
},  
"type" : {  
"type" : "string"  
},  
"verb" : {  
"type" : "string"  
}  
}  
}  
}  
}  
}

Type conflict is this: Mapping conflict! 2 fields are defined as several types  
(string, integer, etc) across the indices that match this pattern. You  
may still be able to use these conflict fields in parts of Kibana, but  
they will be unavailable for functions that require Kibana to know their  
type. Correcting this issue will require reindexing your data.

I know that it's conflicting for the older indecies that were created with a different mapping rules. What about newly created index, will it comply to this new conversion, mapping rules?

---

<div class="post-metadata">

### Author: ![Glen\_Smith](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/glen_smith/32/111656_2.png) [@Glen\_Smith](https://discuss.elastic.co/u/Glen_Smith)
#### Post date: [August 3, 2016, 7:13pm UTC](https://discuss.elastic.co/t/field-type-conflict/56686/2 "2016-08-03T19:13:19Z")

</div>

Moving to Kibana

---

<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:42pm UTC](https://discuss.elastic.co/t/field-type-conflict/56686/3 "2017-07-06T13:42:11Z")

</div>