4 fields are 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.
You will need to reindex some set of the indices being targetted by the data view (legacy: index pattern) that you are using. To convert types you could use an ingest pipeline, for example:
Hi JLeysens
Thanks for your help, let me try it this and will back to you with the results. Not totally sure how to do it but will read the documentation and the related discuss issue as well.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.