Index.mapping.depth.limit not persistent after an index rollover

Elastic Stack Elasticsearch
1

Hi everyone,

I notice that when the current index is rollovered, the index.mapping.depth.limit is not take into account for the new created index.
We are running an elasticsearch cluster and after we have created the first index, we make an elastic api call : PUT _all/_settings?preserve_existing=true with this body :

{  
	"index.mapping.depth.limit" : "100"
}

By making this API call : GET /my-index-*/_settings, we have this result :

 "my-index-1": {
        "settings": {
            "index": {
                "mapping": {
                    "depth": {
                        "limit": "100"
                    }
                }
                .....
}

But when the index is rollovered, the API call response is without the mapping depth limit section, and some errors like Limit of mapping depth [20] has been exceeded due to object field

Is there something we are doing it wrong ?

Thanks for your help
Khaled

2

You need to put this into your template so that the new index is created using that, so take a look at that :slight_smile:

3

Hi Mark,
indeed, it was the correction to implement.
Thx for your help.

BR,
Khaled

4

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