-
Notifications
You must be signed in to change notification settings - Fork 1.3k
DynamicMapping annotation should be applicable to any object field. #1767
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
You can do this by adding the |
I tried, but it is completely ignored, property just mapped as { "type": "object"} without any other settings. There is a check if the property is an entity, and if not - dynamic mapping not applied, and o check for annotation is done in that case. |
Can you provide the entity definition for your case so that this can be reproduced? |
Here is my Field in code:
This is field in elastic:
And this is a check in MappingBuilder:220
So as you can see, nothing Object-related applied at all, if the property isn't an entity. But it isn't. |
fixed in master an backported to 4.2.x, 4.1.x and 4.0.x |
As of the documentation, it is possible to make different values for dynamicMapping setting in document and it's inner objects.
However, it is not possible to enable dynamicMapping for
@Field(type = FieldType.Object)
, because it is not an entity.There should be a way to apply this setting on any property, not only for documents, as there many cases, when Object field is not an entity - Map, for example.
The text was updated successfully, but these errors were encountered: