# Data Type changes after Lifecycle creation

**URL:** <https://discuss.elastic.co/t/data-type-changes-after-lifecycle-creation/262103>\
**Category:** Elasticsearch\
**Created:** [January 25, 2021, 12:33pm UTC](https://discuss.elastic.co/t/data-type-changes-after-lifecycle-creation/262103 "2021-01-25T12:33:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hermlam](https://avatars.discourse-cdn.com/v4/letter/h/8797f3/32.png) [@hermlam](https://discuss.elastic.co/u/hermlam)\
**Post date:** [January 25, 2021, 12:33pm UTC](https://discuss.elastic.co/t/data-type-changes-after-lifecycle-creation/262103/1 "2021-01-25T12:33:22Z")

</div>

Good morning,

I have syslog with special fields. These logs are being processed by Elastic-Agent (Filebeat). I created some extra fields in the datastream with numeric data type. These fields are being filled by a KV-processor in the ingest pipeline. All working well.

But after the creation of a new index through the ‘Lifecycle’ policy, the datatype had been changed to ‘keyword’ and aggregation fails.

What’s the problem here?

Thanks,

Herman

---

<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:** [February 22, 2021, 12:33pm UTC](https://discuss.elastic.co/t/data-type-changes-after-lifecycle-creation/262103/2 "2021-02-22T12:33:27Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.