I have a mapping conflicts in across our indices (separated on a daily basis):
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 re-indexing your data.
Yesterday I changed via logstash
% {NUMBER: bytes: int}
a field called "bytes" from the default type string to integer and today I have the issue.
How can I change the field type on the old indexes?
Thanks, great work! I have a few questions about some points of the blog post:
If I have multiple indexes (for example "logstash-YYYY.MM.DD"), can I do the same thing using as index "logstash- *" or do I have to reschedule the logstash input for each index?
If I don't have a new cluster, but I work on one as input and output, I will overwrite the old data or the data will be duplicated?
You talk about "first creating the mapping we want to apply before indexing any date", but considering the above (multiple indexes and clusters already existing), I can do the same this step?
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.