I think maybe you're right. Let me double check. I might be confusing it with the previous version

Hi JitteryCoyote63 , can I assume you ran all DB migrations without issue?

This is the mapping of the faulty index:
{ "events-plot-d1bd92a3b039400cbafc60a7a5b1e52b_new" : { "mappings" : { "dynamic" : "strict", "properties" : { "@timestamp" : { "type" : "date" }, "iter" : { "type" : "long" }, "metric" : { "type" : "keyword" }, "plot_data" : { "type" : "binary" }, "plot_len" : { "type" : "long" }, "plot_str" : { "type" : "text", "index" : false }, "task" : { "type" : "keyword" }, "timestamp" : { "type" : "date" }, "type" : { "type" : "keyword" }, "value" : { "type" : "float" }, "variant" : { "type" : "keyword" }, "worker" : { "type" : "keyword" } } } } }

To be fully transparent, I did a manual reindexing of the whole ES DB one year ago after it run out of space, at that point I might have changed the mapping to strict, but I am not sure. Could you please confirm that the mapping is correct?

If Elastic isn't crashing then it should be good. Once I get a confirmation I'll update you 🙂

JitteryCoyote63 I think you're right, I see no other explanation...

Hi CostlyOstrich36 , there was no DB migration necessary since 1.6, right?