Skip to content

Commit

Permalink
[doc] Document deprecation of storing nanosecond resolution on date
Browse files Browse the repository at this point in the history
field

relates elastic#78921
  • Loading branch information
pgomulka committed Oct 18, 2021
1 parent d50c9e8 commit 0c4acdb
Showing 1 changed file with 15 additions and 0 deletions.
15 changes: 15 additions & 0 deletions docs/reference/migration/migrate_8_0/mappings.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -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]
Expand Down

0 comments on commit 0c4acdb

Please sign in to comment.