From a9a9048e1096c7f6f109e6530c97852fdcea1d5c Mon Sep 17 00:00:00 2001 From: Steve Gordon Date: Thu, 26 Nov 2020 13:12:18 +0000 Subject: [PATCH] Update date histogram doc (#5108) --- .../date-histogram/date-histogram-aggregation-usage.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/aggregations/bucket/date-histogram/date-histogram-aggregation-usage.asciidoc b/docs/aggregations/bucket/date-histogram/date-histogram-aggregation-usage.asciidoc index 6ea218a7fa3..ce20f2f8d13 100644 --- a/docs/aggregations/bucket/date-histogram/date-histogram-aggregation-usage.asciidoc +++ b/docs/aggregations/bucket/date-histogram/date-histogram-aggregation-usage.asciidoc @@ -19,7 +19,7 @@ A multi-bucket aggregation similar to the histogram except it can only be applie From a functionality perspective, this histogram supports the same features as the normal histogram. The main difference is that the interval can be specified by date/time expressions. -NOTE: When specifying a `format` **and** `extended_bounds` or `missing`, in order for Elasticsearch to be able to parse +NOTE: When specifying a `format` **and** `extended_bounds`, `hard_bounds` or `missing`, in order for Elasticsearch to be able to parse the serialized `DateTime` of `extended_bounds` or `missing` correctly, the `date_optional_time` format is included as part of the `format` value.