Elastic allows us to store data in a field without indexing it with the 'enabled' keyword. This was used for storing coverage information. However the way it was didn't work. This caused coverage to be missing and tests to break.
The mappings._doc._all.enabled path was used in mapping spec, when the correct one should be mappings._doc.enabled.
Without this being applied, the data being stored was too large (too many fields) and Elastic was erroring.
There was no error handling on the coverage generation process, meaning the error that Elastic returned was ignored.
Integration tests were given conflicting names, meaning the tests that showed this weren't running.
Fix is a simple change in the mapping, plus error handling.
afandian
commented
5 years ago
Elastic allows us to store data in a field without indexing it with the 'enabled' keyword. This was used for storing coverage information. However the way it was didn't work. This caused coverage to be missing and tests to break.
mappings._doc._all.enabledpath was used in mapping spec, when the correct one should bemappings._doc.enabled.Fix is a simple change in the mapping, plus error handling.