I'm seeing following through Management's Index Patterns:
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.
- Mapping | Elasticsearch Reference [5.0] | Elastic
- Reindex API | Elasticsearch Reference [5.2] | Elastic
however Kibana still identifies some keys as a conflict (I believe value for that key is