# Change field type from string to integer? and how to re-index?

**URL:** https://discuss.elastic.co/t/change-field-type-from-string-to-integer-and-how-to-re-index/28021
**Category:** Elasticsearch
**Created:** [August 25, 2015, 2:56pm UTC](https://discuss.elastic.co/t/change-field-type-from-string-to-integer-and-how-to-re-index/28021 "2015-08-25T14:56:38Z")
**Posts on this page:** 1
**Showing post:** 13

<div class="post-metadata">

### Author: ![Jeremy\_Colton](https://avatars.discourse-cdn.com/v4/letter/j/51bf81/32.png) [@Jeremy\_Colton](https://discuss.elastic.co/u/Jeremy_Colton)
#### Post date: [May 18, 2016, 8:35am UTC](https://discuss.elastic.co/t/change-field-type-from-string-to-integer-and-how-to-re-index/28021/13 "2016-05-18T08:35:08Z")

</div>

My apologies, I've created a new thread for my re-indexing issue:

> [@Re-index after changing field type from String to Float](https://discuss.elastic.co/t/re-index-after-changing-field-type-from-string-to-float/50317):
>
> Hi, I have a 'duration' field being indexed in my ES as of May 5th 2016. Logstash automatically created it as type String. A few days and a few records later I realised this problem and configured Logstash to set this field's type to Float via the mutate filter. I see in the logstash logs that the field is now being parsed as a Float. In Kibana on the settings page for my logstash-\* index, on clicking the 'refresh field list' link, i see the expected warning: Mapping conflict! A field is d…

---

_[View the full topic](https://discuss.elastic.co/t/change-field-type-from-string-to-integer-and-how-to-re-index/28021)._