$ the-wire · showcase
Spring data elasticsearch fixes nanosecond date formatting
By RepoJournal · Filed · About Spring
Spring Data Elasticsearch shipped a fix for the formatting of `DateFormat.strict_date_optional_time_nanos` in the last 24 hours.
Spring Data Elasticsearch corrected the formatting of `DateFormat.strict_date_optional_time_nanos` [1], addressing issue #3334 [1]. The change ensures that dates using this format are serialized correctly, which matters for fields that need nanosecond precision. In spring-tools, Martin Lippert added handling for concatenated strings when extracting values from JDT AST nodes [2], improving how the IDE tooling parses string literals. The commit also includes a separate formatting change [3]. Spring Batch Extensions saw housekeeping: removing the unused `archunit-junit5` dependency [4] and bumping `wiremock-spring-boot` from 4.2.0 to 4.2.2 [5]. Additionally, Maven plugins were updated [6]. Overall, the changes are routine dependency updates and small fixes, with the most notable being the date formatting correction.
Action items
- → Upgrade Spring Data Elasticsearch to include the nanosecond date formatting fix spring-projects/spring-data-elasticsearch [plan]
- → Review JDT AST extraction changes in spring-tools for impact on your tooling spring-projects/spring-tools [monitor]
- → Monitor the wiremock-spring-boot bump in spring-batch-extensions for compatibility spring-projects/spring-batch-extensions [monitor]
References
- [1] Fix formatting of DateFormat.strict_date_optional_time_nanos. ↗ spring-projects/spring-data-elasticsearch
- [2] GH-1486: deal with concatenated strings when extracting values from JDT AST nodes ↗ spring-projects/spring-tools
- [3] formatting ↗ spring-projects/spring-tools
- [4] Remove unused `archunit-junit5` ↗ spring-projects/spring-batch-extensions
- [5] Bump `wiremock-spring-boot` from 4.2.0 to 4.2.2 ↗ spring-projects/spring-batch-extensions
- [6] Update Maven plugins ↗ spring-projects/spring-batch-extensions