MapperParsingException[failed to parse [a.b.c.subsystem]]; nested: IllegalArgumentException[unknown property [major]];
So all I can do is to eliminate this part of my JSON before sending it to Elasticsearch.
However, it would be helpful if Elasticsearch provided a way to handle this type of JSON structure dynamically.
MapperParsingException[Merging dynamic updates triggered a conflict: mapper [a.bc.subsystem] of different type, current_type [string], merged_type [ObjectMapper]]
This is because I am using dynamic mapping - my JSONs are deeply nested and some branches vary a lot, so I don't want to go through creating the complete index structure myself.
In any case, I now simply pre-process the JSON before sending it to Elasticsearch, this seems to be the most efficient solution.
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.