From 5ed4d40eafd699f11d196e337cc2cbfc954c662e Mon Sep 17 00:00:00 2001 From: QY Date: Tue, 20 Dec 2022 21:01:11 +0800 Subject: [PATCH] [DOCS] Remove outdated note in `Date field type` (#92408) Negative epoch timestamps are supported in 8.2.0 by pr #80208 (cherry picked from commit 7b17e1b5dc9f31f3fefc5cbc880bcb709acdd4b9) --- docs/reference/mapping/types/date.asciidoc | 3 --- 1 file changed, 3 deletions(-) diff --git a/docs/reference/mapping/types/date.asciidoc b/docs/reference/mapping/types/date.asciidoc index e8c21e8f3dc42..4d69ddfd517c8 100644 --- a/docs/reference/mapping/types/date.asciidoc +++ b/docs/reference/mapping/types/date.asciidoc @@ -10,9 +10,6 @@ JSON doesn't have a date data type, so dates in Elasticsearch can either be: * a number representing _milliseconds-since-the-epoch_. * a number representing _seconds-since-the-epoch_ (<>). -NOTE: Values for _milliseconds-since-the-epoch_ must be non-negative. Use a -formatted date to represent dates before 1970. - Internally, dates are converted to UTC (if the time-zone is specified) and stored as a long number representing milliseconds-since-the-epoch.