# Beats return conflicting mapping

**URL:** <https://discuss.elastic.co/t/beats-return-conflicting-mapping/247227>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [September 2, 2020, 11:59am UTC](https://discuss.elastic.co/t/beats-return-conflicting-mapping/247227 "2020-09-02T11:59:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![a\_maze](https://avatars.discourse-cdn.com/v4/letter/a/90ced4/32.png) [@a\_maze](https://discuss.elastic.co/u/a_maze)\
**Post date:** [September 2, 2020, 11:59am UTC](https://discuss.elastic.co/t/beats-return-conflicting-mapping/247227/1 "2020-09-02T11:59:25Z")

</div>

Hello,

I am struggling to get a very basic ElasticStack / filebeat setup running.

Everything was ok while I was using 7.8.1, but since I upgraded to 7.9.0 the Beats have been creating conflicts in my indexes.

It's only a handful of them, but what I am seeing from Kibana compared to what I see on ECS field reference is different, and I don't understand why.

Typically, this is one of the 4 conflicts I've been stuck with for a while:

| Type | Index names |
| --- | --- |
| ip | filebeat-7.8.1-2020.09.02 |
| text | filebeat-7.9.0-2020.08.19, filebeat-7.9.0-2020.08.20, filebeat-7.9.0-2020.08.21, filebeat-7.9.0-2020.08.22, filebeat-7.9.0-2020.08.23, filebeat-7.9.0-2020.08.25, filebeat-7.9.0-2020.08.26, filebeat-7.9.0-2020.08.27, filebeat-7.9.0-2020.08.28, filebeat-7.9.0-2020.08.29, filebeat-7.9.0-2020.08.30, filebeat-7.9.0-2020.08.31, filebeat-7.9.0-2020.09.01, filebeat-7.9.0-2020.09.02 |

According to ECS, `source.ip` should be `ip` type, yet all 7.9.0 are returning `text`.

What am I missing here?

---

<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:** [September 30, 2020, 1:59pm UTC](https://discuss.elastic.co/t/beats-return-conflicting-mapping/247227/2 "2020-09-30T13:59:37Z")

</div>

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