From 0c4acdba9649a4b08f4aa1eb7fbfd34c51f64fec Mon Sep 17 00:00:00 2001 From: pgomulka Date: Mon, 18 Oct 2021 17:56:36 +0200 Subject: [PATCH] [doc] Document deprecation of storing nanosecond resolution on date field relates #78921 --- .../migration/migrate_8_0/mappings.asciidoc | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/docs/reference/migration/migrate_8_0/mappings.asciidoc b/docs/reference/migration/migrate_8_0/mappings.asciidoc index 71721120dd7d7..03b70b37984bb 100644 --- a/docs/reference/migration/migrate_8_0/mappings.asciidoc +++ b/docs/reference/migration/migrate_8_0/mappings.asciidoc @@ -89,6 +89,21 @@ For a detailed migration guide, see the {ref}/migrate-to-java-time.html[Java time migration guide]. ==== +.Attempting to store nanosecond resolution on date field is deprecated +[%collapsible] +==== +*Details* + +Attempting to store a nanosecond resolution on a date field is deprecated. +This behaviour was allowed so far, but was always resulting in resolution loss. +The field of type `date` can only store up to milliseconds resolution. + + +*Impact* + +A deprecation warning will be emitted when attempting to store a nanosecond resolution +on `date` type field. `date_nanos` should be used instead +==== + + [[geo-shape-strategy]] .Several `geo_shape` mapping parameters have been removed. [%collapsible]