# Mapping conflict after upgrade filebeat to to 7.12

**URL:** <https://discuss.elastic.co/t/mapping-conflict-after-upgrade-filebeat-to-to-7-12/268338>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [March 25, 2021, 12:34pm UTC](https://discuss.elastic.co/t/mapping-conflict-after-upgrade-filebeat-to-to-7-12/268338 "2021-03-25T12:34:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![molekuul](https://avatars.discourse-cdn.com/v4/letter/m/e5b9ba/32.png) [@molekuul](https://discuss.elastic.co/u/molekuul)\
**Post date:** [March 25, 2021, 12:34pm UTC](https://discuss.elastic.co/t/mapping-conflict-after-upgrade-filebeat-to-to-7-12/268338/1 "2021-03-25T12:34:02Z")

</div>

Hi,

After the filebeat upgrade from 7.11.1 to 7.12.0 I get an Mapping conflict for field: postgresql.log.error.code

It seems like in 7.11.1 this field has a type long but in 7.12 the type is keyword

How can I fix this?

kind regards,

Joris Weijters

---

<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:** [April 22, 2021, 2:34pm UTC](https://discuss.elastic.co/t/mapping-conflict-after-upgrade-filebeat-to-to-7-12/268338/2 "2021-04-22T14:34:43Z")

</div>

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