From 5a4d4dabbaf881f141dac4560c98075be3c56ec6 Mon Sep 17 00:00:00 2001 From: ashwinkumar12345 Date: Mon, 12 Jul 2021 10:15:32 -0700 Subject: [PATCH] fixed typo --- _opensearch/data-streams.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_opensearch/data-streams.md b/_opensearch/data-streams.md index c52f8d86..91c8a69a 100644 --- a/_opensearch/data-streams.md +++ b/_opensearch/data-streams.md @@ -17,7 +17,7 @@ A typical workflow to manage time-series data is as follows: - To split your data into an index for each day, use the rollover operation. - To perform searches on a virtual index name that gets expanded to the underlying indices, create an [index alias]({{site.url}}{{site.baseurl}}/opensearch/index-alias/). - To perform a write operation on an index alias, configure the latest index as the write index. -- To configure new indices, extract common mappings and settings into an [index template]({{site.url}}{{site.baseurl}}/opensearch/index-templates/)). +- To configure new indices, extract common mappings and settings into an [index template]({{site.url}}{{site.baseurl}}/opensearch/index-templates/). Even after you perform all these operations, you’re still not enforcing the best practices when dealing with time-series data. For example, you can modify the indices directly. You’re able to ingest documents without a timestamp field, which might result in slower queries.