Fix dynamic values and object handling in subobjects: auto
#113672
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Objects and fields with flattened names may not be detected during document parsing, depending on the use of curly brackets for intermediate objects. In this case, dynamic mappers get created for leaf values that may not match the ones in the mapping, e.g. long vs integer. This gets fixed by checking for existing mappers for a given leaf path on value retrieval.
More so, dynamic (empty) objects may be created to match intermediate objects that would otherwise be flattened. For instance, parsing
"foo": { "bar": { "baz": 10 } }
may create a dynamic objectfoo
before realizing that there's an existing objectfoo.bar
containingbaz
. In these cases, the intermediate object should be dropped.Also, split
20_synthetic_source.yml
by moving thecopy_to
tests in a separate file.Related to ##108826