Add support for complex mappings in MappingGenerator#340
Merged
Conversation
2e15f5e to
e6f6a43
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Extends
MappingGeneratorto support full Elasticsearch mapping structures, enabling the use of advanced features likedynamic_templates,dynamicsettings, and other mapping-level configurations.Motivation
Previously,
MappingGeneratoronly supported simple property definitions, automatically wrapping them in apropertieskey. This prevented users from utilizing advanced Elasticsearch mapping features that need to be defined at the mapping root level, such asdynamic_templates.Changes
Detection Logic: The method now detects whether the mapping contains a
propertieskey:propertiesExample Usage: