-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Consider Document as simple type #1675
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
type: task
A general task
Comments
Part of the solution is contributed by #1676. |
mp911de
added a commit
that referenced
this issue
Feb 1, 2021
Document is now a simple type that can be used as target type for complex objects. Writing GeoConverters now serialize objects as Document instead of Map. Since Jackson considers Map-like types as JSON objects, we can safely use Document. Resolves #1675.
mp911de
added a commit
that referenced
this issue
Feb 1, 2021
Fix PersistenceConstructor of Completion to accept the property type String[]. See #1675.
mp911de
added a commit
that referenced
this issue
Feb 2, 2021
We now no longer rely on isSimpleType when writing Maps. This is the preparation to consider Map as simple type. See #1675.
mp911de
added a commit
that referenced
this issue
Feb 2, 2021
mp911de
added a commit
that referenced
this issue
Feb 2, 2021
mp911de
added a commit
that referenced
this issue
Feb 2, 2021
We now no longer rely on isSimpleType when writing Maps. This is the preparation to consider Map as simple type. See #1675.
mp911de
added a commit
that referenced
this issue
Feb 2, 2021
mp911de
added a commit
that referenced
this issue
Feb 2, 2021
mp911de
added a commit
that referenced
this issue
Feb 3, 2021
* Add support for SpEL expressions via @value. * Simplify readCollectionOrArray to consider properly nested lists and maps * Simplify readMap to allow reading generic maps and entities in maps. * Report a fallback TypeInformation in DefaultElasticsearchTypeMapper to properly convert nested maps. We now no longer rely on isSimpleType when writing Maps. This is the preparation to consider Map as simple type. Resolves #1676. See #1675.
mp911de
added a commit
that referenced
this issue
Feb 3, 2021
Fix PersistenceConstructor of Completion to accept the property type String[]. See #1675.
mp911de
added a commit
that referenced
this issue
Feb 3, 2021
sothawo
pushed a commit
that referenced
this issue
Feb 4, 2021
* Add support for SpEL expressions via @value. * Simplify readCollectionOrArray to consider properly nested lists and maps * Simplify readMap to allow reading generic maps and entities in maps. * Report a fallback TypeInformation in DefaultElasticsearchTypeMapper to properly convert nested maps. We now no longer rely on isSimpleType when writing Maps. This is the preparation to consider Map as simple type. Resolves #1676. See #1675. (cherry picked from commit 877de9c)
closed with #1677 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Adding spring-data-elasticsearch to spring project causes multiple warnings in app log, like:
o.s.d.c.CustomConversions - Registering converter from class org.springframework.data.elasticsearch.core.geo.GeoJsonMultiPoint to interface java.util.Map as writing converter although it doesn't convert to a store-supported type! You might want to check your annotation setup at the converter implementation.
More log lines here: log.txt
First of all app shouldn't behave like this, especially considering these converters are not used. And secondly, error message looks irrelevant for me, looks like it was initially created for user converters.
Related classes are:
org/springframework/data/convert/CustomConversions.java
org/springframework/data/elasticsearch/core/convert/ElasticsearchCustomConversions.java
Workaround: https://stackoverflow.com/questions/60001034/how-to-remove-spring-data-customconversions-warnings-from-application-startup
Related issue: spring-projects/spring-data-commons#2043
The text was updated successfully, but these errors were encountered: