Skip to content

[DOCS] Document deprecation of storing nanosecond resolution on date field #79370

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed

[DOCS] Document deprecation of storing nanosecond resolution on date field #79370

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0c4acdb
[doc] Document deprecation of storing nanosecond resolution on date
pgomulka Oct 18, 2021
bda6c07
Apply suggestions from code review
pgomulka Oct 19, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions docs/reference/migration/migrate_8_0/mappings.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -89,6 +89,22 @@ For a detailed migration guide, see the {ref}/migrate-to-java-time.html[Java
time migration guide].
====

.Attempting to store nanosecond resolution in a date field is deprecated.
[%collapsible]
====
*Details* +
Attempting to store a nanosecond resolution in a date field is deprecated.
This behaviour was allowed so far, but was always resulting in resolution loss.
A {ref}/date.html[`date`] field can only store up to millisecond resolutions.


*Impact* +
If you attempt to store a nanosecond resolution in a `date` type field, {es} will
emit a deprecation warning. To avoid deprecation warnings, use a
{ref}/date_nanos.html[`date_nanos`] field instead.
====


[[geo-shape-strategy]]
.Several `geo_shape` mapping parameters have been removed.
[%collapsible]
Expand Down