Mapping Conflict with several types

Elastic Stack Kibana
1

Hi guys,

I'm facing this issues in Data View,

Mapping conflict

A field is defined as several types (string, integer, etc) across the indices that match this pattern. You may still be able to use these conflict fields in parts of Kibana, but they will be unavailable for functions that require Kibana to know their type. Correcting this issue will require reindexing your data.

syslog_timestamp -> date, text (Conflict)

It require reindexing my data.
But I already deleted the indices which is conflict data inside.
But the conflict still there.

Any idea how to resolve this?

2

Hello @wcpoon - Which version of the elastic stack are you running?

Could you capture a har file which includes the request fields_for_wildcard? It will provide useful debugging info.

Thanks,
Matt

3

Hi @mattkime, I'm running in 8.1.2 now.
I already resolved the issues. :slight_smile:
Thanks.

4

@wcpoon mind if you share what solved it? thx!

5

I assigned to another field and different types.

6

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