# What prevents rollover in a mapping?

**URL:** https://discuss.elastic.co/t/what-prevents-rollover-in-a-mapping/358705
**Category:** Kibana
**Tags:** ilm-index-lifecycle-management
**Created:** [May 3, 2024, 11:40am UTC](https://discuss.elastic.co/t/what-prevents-rollover-in-a-mapping/358705 "2024-05-03T11:40:24Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![h.d.intodata](https://avatars.discourse-cdn.com/v4/letter/h/c67d28/32.png) [@h.d.intodata](https://discuss.elastic.co/u/h.d.intodata)
#### Post date: [May 3, 2024, 11:40am UTC](https://discuss.elastic.co/t/what-prevents-rollover-in-a-mapping/358705/1 "2024-05-03T11:40:24Z")

</div>

Hi team,

I have an elasticsearch index which I am wanting to apply an ILM on. I am able to reindex my original index and it preservers the mapping. However, when i try to apply the mapping to a rollover I get :

```auto
"error": {
    "root_cause": [
      {
        "type": "mapper_parsing_exception",
        "reason": "Mapping definition for [host] has unsupported parameters: [settings : {number_of_shards=1, number_of_replicas=1}] [service : {properties={address={type=text, fields={keyword={type=text}}}, type={type=text, fields={keyword={type=text}}}}}] [metricset : {properties={period={type=long}, name={type=text, fields={keyword={type=text}}}}}]

```

This mapping came from the Talend team, which they made to monitoring their tool. Unfortunately, this project is no longer in development and I can't contact them about it. I have no clue what can be causing this mapping not to be in a rollover. If anyone has any advice/guidance that would be greatly appreciated.