From bc35cc99df6e90acc7f0e318add8ead5ed82ee66 Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Wed, 2 Oct 2024 14:31:43 -0400 Subject: [PATCH 1/6] Make a minor change to trigger release note process --- docs/reference/mapping/params/format.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/reference/mapping/params/format.asciidoc b/docs/reference/mapping/params/format.asciidoc index 943e8fb879ff3..5fdf38baa514c 100644 --- a/docs/reference/mapping/params/format.asciidoc +++ b/docs/reference/mapping/params/format.asciidoc @@ -34,13 +34,13 @@ down to the nearest day. Completely customizable date formats are supported. The syntax for these is explained in https://docs.oracle.com/en/java/javase/21/docs/api/java.base/java/time/format/DateTimeFormatter.html[DateTimeFormatter docs]. -Note that whilst the built-in formats for week dates use the ISO definition of weekyears, +Note that while the built-in formats for week dates use the ISO definition of weekyears, custom formatters using the `Y`, `W`, or `w` field specifiers use the JDK locale definition of weekyears. This can result in different values between the built-in formats and custom formats for week dates. [[built-in-date-formats]] -==== Built In Formats +==== Built in formats Most of the below formats have a `strict` companion format, which means that year, month and day parts of the month must use respectively 4, 2 and 2 digits From c7cd63d4b3e5ea21e3e022d2f236ec243531e778 Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Wed, 2 Oct 2024 15:47:06 -0400 Subject: [PATCH 2/6] changelog entry --- docs/changelog/113975.yaml | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 docs/changelog/113975.yaml diff --git a/docs/changelog/113975.yaml b/docs/changelog/113975.yaml new file mode 100644 index 0000000000000..a564c8bc40eb1 --- /dev/null +++ b/docs/changelog/113975.yaml @@ -0,0 +1,19 @@ +pr: 113975 +summary: JDK locale database change +area: Analysis +type: breaking +issues: [] +breaking: + title: JDK locale database change + area: Mapping + details: | + {es} 8.16 changes the version of the JDK that is included from version 22 to version 23. This changes the locale database that is used by Elasticsearch from the COMPAT database to the CLDR database. This change can cause significant differences to the textual date formats accepted by Elasticsearch, and to calculated week-dates. + + If you run {es} 8.16 on JDK version 22 or below, it will use the COMPAT locale database to match the behavior of 8.15. However, starting with {es} 9.0, {es} will use the CLDR database regardless of JDK version it is run on. + impact: | + This affects you if you use custom date formats using textual or week-date field specifiers. If you field specifiers that are incompatible with the CLDR database, then this change will cause Elasticsearch to reject previously valid date fields as invalid data. You might need to modify your ingest or output integration code to account for the differences between these two JDK versions. + + Starting in version 8.15.2, Elasticsearch will log deprecation warnings if you are using date format specifiers that might change on upgrading to JDK 23. These warnings are visible in Kibana. + + For detailed guidance, refer to the https://ela.st/jdk-23-locales[Elastic blog]. + notable: true From ba7ac16107025816febfbef1d0623474a203e72f Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Wed, 2 Oct 2024 15:47:56 -0400 Subject: [PATCH 3/6] update area --- docs/changelog/113975.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/changelog/113975.yaml b/docs/changelog/113975.yaml index a564c8bc40eb1..69944ac383035 100644 --- a/docs/changelog/113975.yaml +++ b/docs/changelog/113975.yaml @@ -1,6 +1,6 @@ pr: 113975 summary: JDK locale database change -area: Analysis +area: Mapping type: breaking issues: [] breaking: From dd8ecc72ee6984146f953a84ee5d9a35b3c31517 Mon Sep 17 00:00:00 2001 From: shainaraskas <58563081+shainaraskas@users.noreply.github.com> Date: Thu, 3 Oct 2024 10:05:49 -0400 Subject: [PATCH 4/6] Apply suggestions from code review --- docs/changelog/113975.yaml | 2 +- docs/reference/mapping/params/format.asciidoc | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/changelog/113975.yaml b/docs/changelog/113975.yaml index 69944ac383035..096d27ceec72a 100644 --- a/docs/changelog/113975.yaml +++ b/docs/changelog/113975.yaml @@ -11,7 +11,7 @@ breaking: If you run {es} 8.16 on JDK version 22 or below, it will use the COMPAT locale database to match the behavior of 8.15. However, starting with {es} 9.0, {es} will use the CLDR database regardless of JDK version it is run on. impact: | - This affects you if you use custom date formats using textual or week-date field specifiers. If you field specifiers that are incompatible with the CLDR database, then this change will cause Elasticsearch to reject previously valid date fields as invalid data. You might need to modify your ingest or output integration code to account for the differences between these two JDK versions. + This affects you if you use custom date formats using textual or week-date field specifiers. If you use date fields or calculated week-dates that change between the COMPAT and CLDR databases, then this change will cause Elasticsearch to reject previously valid date fields as invalid data. You might need to modify your ingest or output integration code to account for the differences between these two JDK versions. Starting in version 8.15.2, Elasticsearch will log deprecation warnings if you are using date format specifiers that might change on upgrading to JDK 23. These warnings are visible in Kibana. diff --git a/docs/reference/mapping/params/format.asciidoc b/docs/reference/mapping/params/format.asciidoc index 5fdf38baa514c..6c82b04eb5fe5 100644 --- a/docs/reference/mapping/params/format.asciidoc +++ b/docs/reference/mapping/params/format.asciidoc @@ -40,7 +40,7 @@ of weekyears. This can result in different values between the built-in formats a for week dates. [[built-in-date-formats]] -==== Built in formats +==== Built-in formats Most of the below formats have a `strict` companion format, which means that year, month and day parts of the month must use respectively 4, 2 and 2 digits From 25747d11dadd26bcc06af92351c4eb4d9771057a Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Tue, 22 Oct 2024 13:50:11 -0400 Subject: [PATCH 5/6] new link --- docs/changelog/113975.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/changelog/113975.yaml b/docs/changelog/113975.yaml index 69944ac383035..314cc92c103b2 100644 --- a/docs/changelog/113975.yaml +++ b/docs/changelog/113975.yaml @@ -15,5 +15,5 @@ breaking: Starting in version 8.15.2, Elasticsearch will log deprecation warnings if you are using date format specifiers that might change on upgrading to JDK 23. These warnings are visible in Kibana. - For detailed guidance, refer to the https://ela.st/jdk-23-locales[Elastic blog]. + For detailed guidance, refer to <>. notable: true From 654306de75093a0e5b64dcaf6a2ed8f2eca8a107 Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Tue, 22 Oct 2024 13:52:02 -0400 Subject: [PATCH 6/6] two links --- docs/changelog/113975.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/changelog/113975.yaml b/docs/changelog/113975.yaml index 8c134c8d63dbc..632ba038271bb 100644 --- a/docs/changelog/113975.yaml +++ b/docs/changelog/113975.yaml @@ -15,5 +15,5 @@ breaking: Starting in version 8.15.2, Elasticsearch will log deprecation warnings if you are using date format specifiers that might change on upgrading to JDK 23. These warnings are visible in Kibana. - For detailed guidance, refer to <>. + For detailed guidance, refer to <> and the https://ela.st/jdk-23-locales[Elastic blog]. notable: true