From 3e451ccddacd2be920535e6331c6efb90754c315 Mon Sep 17 00:00:00 2001 From: Aliaksandr Valialkin Date: Tue, 12 Jan 2021 22:02:55 +0200 Subject: [PATCH] docs/Single-server-VictoriaMetrics.md: typo fix --- README.md | 2 +- docs/Single-server-VictoriaMetrics.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 44aa967b2..f4b64cc22 100644 --- a/README.md +++ b/README.md @@ -1369,7 +1369,7 @@ cache when samples with timestamps older than `now - search.cacheTimestampOffset ## Data updates VictoriaMetrics doesn't support updating already existing sample values to new ones. It stores all the ingested data points -for the same time series with identical timestamps. While is possible substituting old time series with new time series via +for the same time series with identical timestamps. While it is possible substituting old time series with new time series via [removal of old time series](#how-to-delete-timeseries) and then [writing new time series](#backfilling), this approach should be used only for one-off updates. It shouldn't be used for frequent updates because of non-zero overhead related to data removal. diff --git a/docs/Single-server-VictoriaMetrics.md b/docs/Single-server-VictoriaMetrics.md index 44aa967b2..f4b64cc22 100644 --- a/docs/Single-server-VictoriaMetrics.md +++ b/docs/Single-server-VictoriaMetrics.md @@ -1369,7 +1369,7 @@ cache when samples with timestamps older than `now - search.cacheTimestampOffset ## Data updates VictoriaMetrics doesn't support updating already existing sample values to new ones. It stores all the ingested data points -for the same time series with identical timestamps. While is possible substituting old time series with new time series via +for the same time series with identical timestamps. While it is possible substituting old time series with new time series via [removal of old time series](#how-to-delete-timeseries) and then [writing new time series](#backfilling), this approach should be used only for one-off updates. It shouldn't be used for frequent updates because of non-zero overhead related to data removal.