Skip to content

Commit 18739c6

Browse files
consulthysjrodewig
authored andcommitted
[DOCS] Clarify that "now" cannot be used in date_range at index time (#52446)
`date_range` fields do not accept `"now"` as a value of either bounds at indexing time. This corrects an error in the range data type mapping docs.
1 parent f3839d8 commit 18739c6

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/reference/mapping/types/range.asciidoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ PUT range_index/_doc/1?refresh
5454
<1> `date_range` types accept the same field parameters defined by the <<date, `date`>> type.
5555
<2> Example indexing a meeting with 10 to 20 attendees.
5656
<3> Date ranges accept the same format as described in <<ranges-on-dates, date range queries>>.
57-
<4> Example date range using date time stamp. This also accepts <<date-math, date math>> formatting, or "now" for system time.
57+
<4> Example date range using date time stamp. This also accepts <<date-math, date math>> formatting. Note that "now" cannot be used at indexing time.
5858

5959
The following is an example of a <<query-dsl-term-query, term query>> on the `integer_range` field named "expected_attendees".
6060

0 commit comments

Comments
 (0)