github-mirrors/elasticsearch
1
0
Fork 0
mirror of https://github.com/elastic/elasticsearch.git synced 2025-06-29 09:54:06 -04:00
Code Issues Projects Releases Packages Wiki Activity

[DOCS] [7.x] Document deprecation of storing nanosecond resolution on date field (#79554)

Browse source 
relates #78921
This commit is contained in:
Przemyslaw Gomulka 2021-10-20 15:37:07 +02:00 • committed by GitHub
parent 9461cc4695
commit 69cf4a3154
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 18 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

15
docs/reference/migration/migrate_7_16.asciidoc
View file

@ -347,4 +347,19 @@ cache do not expire.
To override the defaults, configure the `script.cache.max_size`, To override the defaults, configure the `script.cache.max_size`,
`script.max_compilations_rate`, and `script.cache.expire` settings. `script.max_compilations_rate`, and `script.cache.expire` settings.
==== ====
.Attempting to store nanosecond resolution in a `date` field is deprecated.
[%collapsible]
====
*Details* +
Attempting to store a nanosecond resolution in a {ref}/date.html[`date`] field is deprecated.
While previously allowed, these attempts always resulted in resolution loss.
A `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.
====
// end::notable-breaking-changes[] // end::notable-breaking-changes[]