Skip to content

Commit 0c4acdb

Browse files
committed
[doc] Document deprecation of storing nanosecond resolution on date
field relates elastic#78921
1 parent d50c9e8 commit 0c4acdb

File tree

1 file changed

+15
-0
lines changed

1 file changed

+15
-0
lines changed

docs/reference/migration/migrate_8_0/mappings.asciidoc

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -89,6 +89,21 @@ For a detailed migration guide, see the {ref}/migrate-to-java-time.html[Java
8989
time migration guide].
9090
====
9191

92+
.Attempting to store nanosecond resolution on date field is deprecated
93+
[%collapsible]
94+
====
95+
*Details* +
96+
Attempting to store a nanosecond resolution on a date field is deprecated.
97+
This behaviour was allowed so far, but was always resulting in resolution loss.
98+
The field of type `date` can only store up to milliseconds resolution.
99+
100+
101+
*Impact* +
102+
A deprecation warning will be emitted when attempting to store a nanosecond resolution
103+
on `date` type field. `date_nanos` should be used instead
104+
====
105+
106+
92107
[[geo-shape-strategy]]
93108
.Several `geo_shape` mapping parameters have been removed.
94109
[%collapsible]

0 commit comments

Comments
 (0)