# Failed to parse mapping \[doc\]: Mapping definition for \[error\] has unsupported parameters

**URL:** <https://discuss.elastic.co/t/failed-to-parse-mapping-doc-mapping-definition-for-error-has-unsupported-parameters/109797>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [November 30, 2017, 4:29pm UTC](https://discuss.elastic.co/t/failed-to-parse-mapping-doc-mapping-definition-for-error-has-unsupported-parameters/109797 "2017-11-30T16:29:07Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![quanta84](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/quanta84/32/21902_2.png) [@quanta84](https://discuss.elastic.co/u/quanta84)\
**Post date:** [November 30, 2017, 4:29pm UTC](https://discuss.elastic.co/t/failed-to-parse-mapping-doc-mapping-definition-for-error-has-unsupported-parameters/109797/1 "2017-11-30T16:29:07Z")

</div>

I have just upgraded filebeat from 5.6.4 to 6.0.0 and logs are being flooded with:

> 2017/11/30 16:24:23.327596 client.go:465: WARN Can not index event (status=400): {"type":"mapper\_parsing\_exception","reason":"Failed to parse mapping [doc]: Mapping definition for [error] has unsupported parameters: [properties : {code={type=long}, message={norms=false, type=text}, type={ignore\_above=1024, type=keyword}}]","caused\_by":{"type":"mapper\_parsing\_exception","reason":"Mapping definition for [error] has unsupported parameters: [properties : {code={type=long}, message={norms=false, type=text}, type={ignore\_above=1024, type=keyword}}]"}}

and there is no logs were sent to Elasticsearch.

Config file:

```
filebeat.prospectors:
- type: log
  paths:
   - '/var/lib/docker/containers/*/*.log'
  json.message_key: log
  json.keys_under_root: true
  processors:
  - add_docker_metadata: ~
output.elasticsearch:
  ...

```

Elasticsearch version: 6.0.0

---

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [November 30, 2017, 10:10pm UTC](https://discuss.elastic.co/t/failed-to-parse-mapping-doc-mapping-definition-for-error-has-unsupported-parameters/109797/2 "2017-11-30T22:10:00Z")

</div>

You have any field named `error` in your JSON document?

---

<div class="post-metadata">

**Author:** ![quanta84](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/quanta84/32/21902_2.png) [@quanta84](https://discuss.elastic.co/u/quanta84)\
**Post date:** [December 5, 2017, 7:32am UTC](https://discuss.elastic.co/t/failed-to-parse-mapping-doc-mapping-definition-for-error-has-unsupported-parameters/109797/3 "2017-12-05T07:32:52Z")

</div>

This fixed my problem: [Filebeat v6 and elasticsearch v6](https://discuss.elastic.co/t/filebeat-v6-and-elasticsearch-v6/107925/6?u=quanta84)

---

<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:** [January 2, 2018, 7:32am UTC](https://discuss.elastic.co/t/failed-to-parse-mapping-doc-mapping-definition-for-error-has-unsupported-parameters/109797/4 "2018-01-02T07:32:54Z")

</div>

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