# Parsing Failure with Elasticsearch Index Mapping

**URL:** <https://discuss.elastic.co/t/parsing-failure-with-elasticsearch-index-mapping/231586>\
**Category:** Elasticsearch\
**Created:** [May 7, 2020, 4:31pm UTC](https://discuss.elastic.co/t/parsing-failure-with-elasticsearch-index-mapping/231586 "2020-05-07T16:31:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![zsanford](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zsanford/32/67894_2.png) [@zsanford](https://discuss.elastic.co/u/zsanford)\
**Post date:** [May 7, 2020, 4:31pm UTC](https://discuss.elastic.co/t/parsing-failure-with-elasticsearch-index-mapping/231586/1 "2020-05-07T16:31:15Z")

</div>

I have a Graylog server setup with Elasticsearch and every so often when it creates a new index, I start getting indexer failure messages in Graylog. The error message type is “mapper\_parsing\_exception” and it is always associated with a winlogbeat\_event\_data\_paramX (where X is a number). The error is because it is trying to parse the parameter as a Date type.

When I go and look at the mapping on the server the parameter is set as a Date type. However, when I look at the mapping of the previous index, the same parameter is set to the keyword type. My question is why is this changing when a new index rolls over, why won’t it just stay as a keyword?

I have searched online, but have come up with very little. I someone could shed some light on my situation it would be greatly appreciated.

---

<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:** [June 4, 2020, 4:31pm UTC](https://discuss.elastic.co/t/parsing-failure-with-elasticsearch-index-mapping/231586/2 "2020-06-04T16:31:29Z")

</div>

Closed on June 4, 2020, 4:31pm UTC

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