Thanks I believe I figured it out. But now I'm getting a conflict on the duration field because I created a duration field manually earlier and now the pipeline is trying to create or store the wrong values in it. What is the best way to fix this? Can I remove fields?
If this was done inside the index mapping, then either update the mapping, or change the pipeline so that it creates a field that can be indexed according to that mapping.
If this was done upstream, I am not 100% sure what the issue is. The pipeline should be able to overwrite fields without any issues. But if you just want to drop the previous duration field: Remove processor | Elasticsearch Guide [8.11] | Elastic should work.
It seems I have 3 types in one field Field Type Conflict: The type of this field changes across indices. It is unavailable for many analysis functions. The indices per type are as follows:
field types: text, integer, long
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.