Read/write converters not working [DATAMONGO-2400]

[spring-projects-issues]

Sparow199 opened DATAMONGO-2400 and commented

2019-10-30 12:10:53.107 [restartedMain] WARN o.s.data.convert.CustomConversions - Registering converter from class java.time.LocalDateTime to class org.joda.time.LocalDateTime as reading converter although it doesn't convert from a store-supported type! You might wanna check you annotation setup at the converter implementation. 2019-10-30 12:10:53.115 [restartedMain] WARN o.s.data.convert.CustomConversions - Registering converter from class java.time.LocalDateTime to class org.joda.time.LocalDateTime as reading converter although it doesn't convert from a store-supported type! You might wanna check you annotation setup at the converter implementation. 2019-10-30 12:10:53.117 [restartedMain] WARN o.s.data.convert.CustomConversions - Registering converter from class java.time.LocalDateTime to class java.time.Instant as reading converter although it doesn't convert from a store-supported type! You might wanna check you annotation setup at the converter implementation. 2019-10-30 12:10:53.117 [restartedMain] WARN o.s.data.convert.CustomConversions - Registering converter from class java.time.Instant to class java.time.LocalDateTime as reading converter although it doesn't convert from a store-supported type! You might wanna check you annotation setup at the converter implementation.

After upgrading to v2.1.9+ and 2.2.0+

---

Affects: 2.1.12 (Lovelace SR12), 2.2.1 (Moore SR1)

Reference URL: spring-projects/spring-boot#18817

Issue Links:

• DATACMNS-1615 Allow fine grained store specific converter registration

• DATAMONGO-2458 Make Spring Data MongoDB work with java.time types out-of-the-box

Referenced from: pull request #810, and commits 3b6880e, e9d14f4, 6d54b25, ee6276f, 6278d00

1 votes, 12 watchers

[spring-projects-issues]

rougou commented

I'm getting these warnings, too, but the application seems to work.

Does this have any effect on the date conversions?

[spring-projects-issues]

Sparow199 commented

I finally resolved the problem with application startup. The main cause was an issue with Jedis 2.9.3 on 2.1.9+ and 2.2.0+.

The warning still there but switching to Lettuce solved the problem

[spring-projects-issues]

Christoph Strobl commented

The warnings should not have any effect on the application. 

SpringData commons registers the java.time converters by default for quite some time now and considers them simple types that can be handled by the store itself. This unfortunately is not true for all stores. MongoDB requires the non default Jsr310CodecProvider to be registered with the driver to handle eg. Instant correctly. So the change in commons broke spring data converter registration for those types in Spring Data MongoDB, which we fixed there with the last release. As a side effect, the warnings now appear again.

We're looking into it

[spring-projects-issues]

ibti gja commented

Is the issue still there with spring boot 2.3+ and  mongodb-driver-core 4.0.4 ?
because at the moment I get the same error , but I have override the MongoCustomConversions

[spring-projects-issues]

Tita commented

Hello,

I get the same error with spring boot 2.3+ and mongo-java-driver 3.12.6. Is the issue still there ?
This is a migration classic application with spring to springboot 2.3.1.

Thanks,

[jenshoffmann1331]

Hi @christophstrobl,

we get the warning in a fresh setup with 2.4.5. You wrote the warning should have been fixed. We certainly miss something else. Do you have any clue why we still get that warning?

[arturbdr]

Using Spring boot 2.5.6 with spring-boot-starter-data-mongodb (2.5.6) and mongodb-driver-sync (4.2.3) still gives the warning on project startup.

[marbrink]

I have the same issue on Spring Boot 2.5.5 / Spring Data MongoDB 3.2.5