# Mappings restore errors
**URL:** https://discuss.elastic.co/t/mappings-restore-errors/282417
**Category:** Elasticsearch
**Created:** [August 24, 2021, 10:53pm UTC](https://discuss.elastic.co/t/mappings-restore-errors/282417 "2021-08-24T22:53:44Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@Leonardo\_De\_Oliveira](https://discuss.elastic.co/u/Leonardo_De_Oliveira)
#### Post date: [August 24, 2021, 10:53pm UTC](https://discuss.elastic.co/t/mappings-restore-errors/282417/1 "2021-08-24T22:53:44Z")
Hello Folks!
I am currently running Elasticsearch v5.5.2 in production, and I am setting up a downsized version in our Staging environment.
I used elasticdump v6.67.1 to dump our mappings and a subset of our data which i am trying to restore into ES in staging, the problem comes that when i run the restore the current message appears:
> {"root\_cause":[{"type":"mapper\_parsing\_exception","reason":"Mapping definition for [fields] has unsupported parameters: [fielddata : false]"}],"type":"mapper\_parsing\_exception","reason":"Mapping definition for [fields] has unsupported parameters: [fielddata : false]"}
I am not sure what the issue maybe, i have tried removing all instances of Fielddata=false in the mappings but i am not sure which mapping is causing the problem. has anyone seen this issue before?
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [August 25, 2021, 12:43am UTC](https://discuss.elastic.co/t/mappings-restore-errors/282417/2 "2021-08-25T00:43:32Z")
Welcome to our community! 😃
> [@Leonardo\_De\_Oliveira](#):
>
> I am currently running Elasticsearch v5.5.2 in production
5.X has been [EOL](https://www.elastic.co/support/eol) for quite some time now, please upgrade 🙂
> [@Leonardo\_De\_Oliveira](#):
>
> I am not sure what the issue maybe, i have tried removing all instances of Fielddata=false in the mappings but i am not sure which mapping is causing the problem. has anyone seen this issue before?
It'd help if you could share the mapping.
---
### Author:  [@Leonardo\_De\_Oliveira](https://discuss.elastic.co/u/Leonardo_De_Oliveira)
#### Post date: [August 25, 2021, 11:22am UTC](https://discuss.elastic.co/t/mappings-restore-errors/282417/3 "2021-08-25T11:22:54Z")
Sadly we have a legacy app which is running loopback 3, which can't run on ES newer than 5.x. ☹
We have a plan to sunset it in the next year, until then I have to keep the Prod one running and setup a Staging version of it for testing purposes.
Regarding the mappings here you go. 😃
>
Any help is appreciated 🙂
---
### Author:  [@Leonardo\_De\_Oliveira](https://discuss.elastic.co/u/Leonardo_De_Oliveira)
#### Post date: [August 25, 2021, 2:37pm UTC](https://discuss.elastic.co/t/mappings-restore-errors/282417/4 "2021-08-25T14:37:35Z")
Update:
I am able to restore the mappings syncConversations & ConversationMappings sucessfully.
counts and Communications are the mappings that return:
```auto
{
"error": {
"root_cause": [
{
"type": "mapper_parsing_exception",
"reason": "Mapping definition for [fields] has unsupported parameters: [fielddata : false]"
}
],
"type": "mapper_parsing_exception",
"reason": "Mapping definition for [fields] has unsupported parameters: [fielddata : false]"
},
"status": 400
}
```
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [September 22, 2021, 2:37pm UTC](https://discuss.elastic.co/t/mappings-restore-errors/282417/5 "2021-09-22T14:37:41Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.