OpenSearch/plugin/ml
Dimitris Athanasiou 2aeff7713c [ML] Parsing objects from internal indices should be lenient (elastic/x-pack-elasticsearch#4256)
All ML objects stored in internal indices are currently parsed
strictly. This means unknown fields lead to parsing failures.
In turn, this means we cannot add new fields in any of those
objects (e.g. bucket, record, calendar, etc.) as it is not
backwards compatible.

This commit changes this by introducing lenient parsing when
it comes to reading those objects from the internal indices.
Note we still use strict parsing for the objects we read from
the c++ process, which is nice as it guarantees we would detect
if any of the fields were renamed on one side but not the other.

Also note that even though this is going in from 6.3, we cannot
introduce new fields until 7.0.

relates elastic/x-pack-elasticsearch#4232

Original commit: elastic/x-pack-elasticsearch@3f95d3c7b9
2018-03-29 17:32:57 +01:00
..
cpp-snapshot [ML] Adjust the name of the ML C++ repo (elastic/x-pack-elasticsearch#4020) 2018-03-09 22:53:38 +00:00
licenses More license file corrections 2018-01-18 16:34:25 -08:00
src [ML] Parsing objects from internal indices should be lenient (elastic/x-pack-elasticsearch#4256) 2018-03-29 17:32:57 +01:00
build.gradle [ML] Adjust the name of the ML C++ repo (elastic/x-pack-elasticsearch#4020) 2018-03-09 22:53:38 +00:00