# ELastic search reindexing automation **URL:** \ **Category:** Elasticsearch\ **Created:** [December 18, 2019, 7:25pm UTC](https://discuss.elastic.co/t/elastic-search-reindexing-automation/212393 "2019-12-18T19:25:29Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![kumar6](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kumar6/32/55327_2.png) [@kumar6](https://discuss.elastic.co/u/kumar6)\ **Post date:** [December 18, 2019, 7:25pm UTC](https://discuss.elastic.co/t/elastic-search-reindexing-automation/212393/1 "2019-12-18T19:25:29Z")
Hi, I ran into kibana mapping conflict issue after updating data types for some fields. The only option i have is to reindex the old data to resolve this issue. We have hourly indices with 30 days of data. Can you please suggest best way to automate the process. ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [December 19, 2019, 10:26am UTC](https://discuss.elastic.co/t/elastic-search-reindexing-automation/212393/2 "2019-12-19T10:26:04Z")
Take a look at the [reindex API](https://www.elastic.co/guide/en/elasticsearch/reference/7.5/docs-reindex.html) in combination with an [index template](https://www.elastic.co/guide/en/elasticsearch/reference/7.5/indices-templates.html) that has your field mapped properly. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 16, 2020, 10:26am UTC](https://discuss.elastic.co/t/elastic-search-reindexing-automation/212393/3 "2020-01-16T10:26:10Z")
Closed on January 16, 2020, 10:26am UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.