Spring Data 2025.1.0-M5 released

On behalf of the team and everyone who has contributed, I am pleased to announce the fourth milestone for the next Spring Data generation. This milestone continues delivering new features, refinements, and dependency upgrades.

Updated MongoDB UUID Format Defaults

Spring Data MongoDB now defaults to the BSON binary subtype 4 to represent UUIDs migrating off the legacy subtype 3. While this change doesn’t manifest in a breaking code change, any existing data stored in MongoDB using subtype 3 will not be read correctly and will either require migrating to BSON binary subtype 4 or switching the default back to subtype 3 until the migration is complete.

This is a rather subtle change that only shows its effect on existing data. We’re strongly considering to remove any defaulting, including the BigDecimal and BigInteger format defaults in favor of an explicit configuration to avoid any surprises in the future. If you have any feedback on this topic, please let us know via GitHub.

Composite Identifiers in Spring Data R2DBC

Spring Data R2DBC ships with Composite Id support and full support for embeddables. Composite identifiers can now be complex types, ideally a type with a set of simple properties. A simple example would look like:

class Person {
    @Id Name id; 
    String nickname;
    Integer age;
}

record Name(String first, String last) {
}

While it is not necessary (complex @Id types are considered embeddables) for simple arrangements, you can use @Embedded(prefix=…) to configure column name prefixes.

We aim to ship Jackson 3 support with the next milestone. Refer to our detailed release notes for a complete list of changes.

Thanks to all those who have contributed with issue reports and pull requests.

2025.1.0-M5

THE END
喜欢就支持一下吧
点赞6 分享
评论 抢沙发

请登录后发表评论

    暂无评论内容