# Mapper parser exception when creating an index with mapping
**URL:** https://discuss.elastic.co/t/mapper-parser-exception-when-creating-an-index-with-mapping/235833
**Category:** Elasticsearch
**Created:** [June 4, 2020, 6:10pm UTC](https://discuss.elastic.co/t/mapper-parser-exception-when-creating-an-index-with-mapping/235833 "2020-06-04T18:10:56Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@Sesha\_Sai\_Suhash\_Des](https://discuss.elastic.co/u/Sesha_Sai_Suhash_Des)
#### Post date: [June 4, 2020, 6:10pm UTC](https://discuss.elastic.co/t/mapper-parser-exception-when-creating-an-index-with-mapping/235833/1 "2020-06-04T18:10:56Z")
I am getting error when running the following command. I am a noob please help me.
**command :**
`PUT /companydatabase?pretty { "mappings": { "employees": { "properties": { "FirstName": { "type": "text" }, "LastName": { "type": "text" }, "Designation": { "type": "text" }, "Salary": { "type": "integer" }, "DateOfJoining": { "type": "date", "format": "yyyy-MM-dd" }, "Address": { "type": "text" }, "Gender": { "type": "text" }, "Age": { "type": "integer" }, "MaritalStatus": { "type": "text" }, "Interests": { "type": "text" } } } } }`
**The error :**
`{ "error" : { "root_cause" : [{ "type" : "mapper_parsing_exception", "reason" : "Root mapping definition has unsupported parameters: [employees : {properties={Designation={type=text}, Salary={type=integer}, MaritalStatus={type=text}, DateOfJoining={format=yyyy-MM-dd, type=date}, Address={type=text}, FirstName={type=text}, LastName={type=text}, Gender={type=text}, Age={type=integer}, Interests={type=text}}}]" } ], "type" : "mapper_parsing_exception", "reason" : "Failed to parse mapping [_doc]: Root mapping definition has unsupported parameters: [employees : {properties={Designation={type=text}, Salary={type=integer}, MaritalStatus={type=text}, DateOfJoining={format=yyyy-MM-dd, type=date}, Address={type=text}, FirstName={type=text}, LastName={type=text}, Gender={type=text}, Age={type=integer}, Interests={type=text}}}]", "caused_by" : { "type" : "mapper_parsing_exception", "reason" : "Root mapping definition has unsupported parameters: [employees : {properties={Designation={type=text}, Salary={type=integer}, MaritalStatus={type=text}, DateOfJoining={format=yyyy-MM-dd, type=date}, Address={type=text}, FirstName={type=text}, LastName={type=text}, Gender={type=text}, Age={type=integer}, Interests={type=text}}}]" } }, "status" : 400 }`
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [June 4, 2020, 7:28pm UTC](https://discuss.elastic.co/t/mapper-parser-exception-when-creating-an-index-with-mapping/235833/2 "2020-06-04T19:28:15Z")
Welcome!
I guess you're on 7.x.
Remove `employees` as types have been removed.
---
### Author:  [@Sesha\_Sai\_Suhash\_Des](https://discuss.elastic.co/u/Sesha_Sai_Suhash_Des)
#### Post date: [June 9, 2020, 9:39am UTC](https://discuss.elastic.co/t/mapper-parser-exception-when-creating-an-index-with-mapping/235833/3 "2020-06-09T09:39:20Z")
I am sorry. I don't understand.
Should I remove employees?
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [June 9, 2020, 10:03am UTC](https://discuss.elastic.co/t/mapper-parser-exception-when-creating-an-index-with-mapping/235833/4 "2020-06-09T10:03:26Z")
You should remove the `employees` key from your json.
```
PUT /companydatabase
{ "mappings": { "properties": { "FirstName": { "type": "text" }, "LastName": { "type": "text" }, "Designation": { "type": "text" }, "Salary": { "type": "integer" }, "DateOfJoining": { "type": "date", "format": "yyyy-MM-dd" }, "Address": { "type": "text" }, "Gender": { "type": "text" }, "Age": { "type": "integer" }, "MaritalStatus": { "type": "text" }, "Interests": { "type": "text" } } } }
```
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 7, 2020, 10:03am UTC](https://discuss.elastic.co/t/mapper-parser-exception-when-creating-an-index-with-mapping/235833/5 "2020-07-07T10:03:29Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.