You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CustomConversions registers default converters (such as Joda-Time, JSR-310, JSR-310 Backport) for all stores. This is behavior is limiting for stores, that come with native support for a type that is currently converted through one of the default converters.
Datastax Cassandra Driver and MongoDB Driver 3.8 come with converters for some JSR-310 types. Leveraging driver support gets Spring Data converters out of the way so drivers are responsible for reading and writing such types.
Ideally, we find an approach that allows selective registration of converters (e.g. CustomConversions accepting a Predicate<ConvertiblePair>)
Issue Links:
DATAMONGO-2017 Use driver codec for Instant, LocalTime, LocalDate, and LocalDateTime
("is depended on by")
DATAMONGO-2012 Upgrade to MongoDB java driver 3.8 and reactive streams 1.9
DATAMONGO-2014 Millis precision vs. nano precision of java.time.Instant on Java 10+
The text was updated successfully, but these errors were encountered:
Mark Paluch opened DATACMNS-1349 and commented
CustomConversions
registers default converters (such as Joda-Time, JSR-310, JSR-310 Backport) for all stores. This is behavior is limiting for stores, that come with native support for a type that is currently converted through one of the default converters.Datastax Cassandra Driver and MongoDB Driver 3.8 come with converters for some JSR-310 types. Leveraging driver support gets Spring Data converters out of the way so drivers are responsible for reading and writing such types.
Ideally, we find an approach that allows selective registration of converters (e.g.
CustomConversions
accepting aPredicate<ConvertiblePair>
)Issue Links:
DATAMONGO-2017 Use driver codec for Instant, LocalTime, LocalDate, and LocalDateTime
("is depended on by")
DATAMONGO-2012 Upgrade to MongoDB java driver 3.8 and reactive streams 1.9
DATAMONGO-2014 Millis precision vs. nano precision of java.time.Instant on Java 10+
The text was updated successfully, but these errors were encountered: