Skip to content

Commit edf5bd2

Browse files
authored
Fix typo in try-esql.md (elastic#1615)
h/t @davismcphee
1 parent 1eea6ab commit edf5bd2

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

explore-analyze/discover/try-esql.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -108,7 +108,7 @@ If you’d like to keep the visualization and add it to a dashboard, you can sav
108108
109109
By default, ES|QL identifies time series data when an index contains a `@timestamp` field. This enables the time range selector and visualization options for your query.
110110
111-
If your index doesn’t have an explicit `@timestamp` field, but has a different time field, you can still enable the time range selector and visualization options by calling the `?_start` and `?_tend` parameters in your query.
111+
If your index doesn’t have an explicit `@timestamp` field, but has a different time field, you can still enable the time range selector and visualization options by calling the `?_tstart` and `?_tend` parameters in your query.
112112
113113
For example, the eCommerce sample data set doesn’t have a `@timestamp` field, but has an `order_date` field.
114114
@@ -123,7 +123,7 @@ FROM kibana_sample_data_ecommerce
123123
:alt: ESQL query without time series capabilities enabled
124124
:::
125125

126-
While still querying the same data set, by adding the `?_start` and `?_tend` parameters based on the `order_date` field, **Discover** enables times series capabilities.
126+
While still querying the same data set, by adding the `?_tstart` and `?_tend` parameters based on the `order_date` field, **Discover** enables times series capabilities.
127127

128128
```esql
129129
FROM kibana_sample_data_ecommerce

0 commit comments

Comments
 (0)