From 93a009c3c9478dc29c449f6b3dde55a64439e73b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Istv=C3=A1n=20Zolt=C3=A1n=20Szab=C3=B3?= Date: Tue, 13 Jul 2021 09:33:58 +0200 Subject: [PATCH] [DOCS] Clarifies behavior of datafeeds with or without an end time (#1754) --- .../stack/ml/anomaly-detection/ml-datafeeds.asciidoc | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/docs/en/stack/ml/anomaly-detection/ml-datafeeds.asciidoc b/docs/en/stack/ml/anomaly-detection/ml-datafeeds.asciidoc index f5338a40a..dcc30ad7c 100644 --- a/docs/en/stack/ml/anomaly-detection/ml-datafeeds.asciidoc +++ b/docs/en/stack/ml/anomaly-detection/ml-datafeeds.asciidoc @@ -23,9 +23,14 @@ the {ref}/ml-put-datafeed.html[create {dfeeds} API]. To start retrieving data from {es}, you must start the {dfeed}. When you start it, you can optionally specify start and end times. If you do not specify an -end time, the {dfeed} runs continuously. You can start and stop {dfeeds} in -{kib} or use the {ref}/ml-start-datafeed.html[start {dfeeds}] and -{ref}/ml-stop-datafeed.html[stop {dfeeds}] APIs. A {dfeed} can be started and +end time, the {dfeed} runs continuously. {dfeeds-cap} with an end time close +their corresponding jobs when they are stopped. For this reason, when historical +data is analysed, there is no need to stop the datafeed and/or close the job as +they are stopped and closed automatically when the end time is reached. However, +when a {dfeed} without an end time is stopped, it does not close the +corresponding job automatically. You can start and stop {dfeeds} in {kib} or use +the {ref}/ml-start-datafeed.html[start {dfeeds}] and +{ref}/ml-stop-datafeed.html[stop {dfeeds}] APIs. A {dfeed} can be started and stopped multiple times throughout its lifecycle. [IMPORTANT]