From e92f347336f9cbe23c5b5fd622bc69ccafb83242 Mon Sep 17 00:00:00 2001 From: Aliaksandr Valialkin Date: Wed, 11 Sep 2024 09:39:17 +0200 Subject: [PATCH] docs/VictoriaLogs/querying/README.md: typo fixes: use field_values instead field_names where needed --- docs/VictoriaLogs/querying/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/VictoriaLogs/querying/README.md b/docs/VictoriaLogs/querying/README.md index 95ae6bc31..435e90f11 100644 --- a/docs/VictoriaLogs/querying/README.md +++ b/docs/VictoriaLogs/querying/README.md @@ -650,7 +650,7 @@ Below is an example JSON output returned from this endpoint: } ``` -The `/select/logsql/stream_field_names` endpoint supports optional `limit=N` query arg, which allows limiting the number of returned values to `N`. +The `/select/logsql/stream_field_values` endpoint supports optional `limit=N` query arg, which allows limiting the number of returned values to `N`. The endpoint returns arbitrary subset of values if their number exceeds `N`, so `limit=N` cannot be used for pagination over big number of field values. When the `limit` is reached, `hits` are zeroed, since they cannot be calculated reliably. @@ -761,7 +761,7 @@ Below is an example JSON output returned from this endpoint: } ``` -The `/select/logsql/field_names` endpoint supports optional `limit=N` query arg, which allows limiting the number of returned values to `N`. +The `/select/logsql/field_values` endpoint supports optional `limit=N` query arg, which allows limiting the number of returned values to `N`. The endpoint returns arbitrary subset of values if their number exceeds `N`, so `limit=N` cannot be used for pagination over big number of field values. When the `limit` is reached, `hits` are zeroed, since they cannot be calculated reliably.