From eba4dba07e50c73b7e1acc14f2a153d7f659aa45 Mon Sep 17 00:00:00 2001 From: Valeriy Khakhutskyy <1292899+valeriy42@users.noreply.github.com> Date: Tue, 4 Feb 2025 15:57:57 +0100 Subject: [PATCH 1/2] Mark MlFlushJobRequest as deprecated with future version notice --- specification/ml/flush_job/MlFlushJobRequest.ts | 1 + 1 file changed, 1 insertion(+) diff --git a/specification/ml/flush_job/MlFlushJobRequest.ts b/specification/ml/flush_job/MlFlushJobRequest.ts index 225b85321a..dca143fc52 100644 --- a/specification/ml/flush_job/MlFlushJobRequest.ts +++ b/specification/ml/flush_job/MlFlushJobRequest.ts @@ -35,6 +35,7 @@ import { DateTime } from '@_types/Time' * @availability stack since=5.4.0 stability=stable * @availability serverless stability=stable visibility=public * @cluster_privileges manage_ml + * @deprecated 9.1.0 Forcing any buffered data to be processed is deprecated, in a future major version a datafeed will be required. * @doc_tag ml anomaly * @doc_id ml-flush-job */ From a761a6725e5c6cc7fc063346ee2b1ca1374f46de Mon Sep 17 00:00:00 2001 From: Valeriy Khakhutskyy <1292899+valeriy42@users.noreply.github.com> Date: Thu, 6 Feb 2025 11:05:32 +0100 Subject: [PATCH 2/2] Add schema.json changes --- output/schema/schema.json | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/output/schema/schema.json b/output/schema/schema.json index 43b223d347..31e1660e82 100644 --- a/output/schema/schema.json +++ b/output/schema/schema.json @@ -11272,6 +11272,10 @@ "stability": "stable" } }, + "deprecation": { + "description": "Forcing any buffered data to be processed is deprecated, in a future major version a datafeed will be required.", + "version": "9.1.0" + }, "description": "Force buffered data to be processed.\nThe flush jobs API is only applicable when sending data for analysis using\nthe post data API. Depending on the content of the buffer, then it might\nadditionally calculate new results. Both flush and close operations are\nsimilar, however the flush is more efficient if you are expecting to send\nmore data for analysis. When flushing, the job remains open and is available\nto continue analyzing data. A close operation additionally prunes and\npersists the model state to disk and the job must be opened again before\nanalyzing further data.", "docId": "ml-flush-job", "docTag": "ml anomaly", @@ -170827,6 +170831,10 @@ } ] }, + "deprecation": { + "description": "Forcing any buffered data to be processed is deprecated, in a future major version a datafeed will be required.", + "version": "9.1.0" + }, "description": "Force buffered data to be processed.\nThe flush jobs API is only applicable when sending data for analysis using\nthe post data API. Depending on the content of the buffer, then it might\nadditionally calculate new results. Both flush and close operations are\nsimilar, however the flush is more efficient if you are expecting to send\nmore data for analysis. When flushing, the job remains open and is available\nto continue analyzing data. A close operation additionally prunes and\npersists the model state to disk and the job must be opened again before\nanalyzing further data.", "inherits": { "type": { @@ -170914,7 +170922,7 @@ } } ], - "specLocation": "ml/flush_job/MlFlushJobRequest.ts#L24-L107" + "specLocation": "ml/flush_job/MlFlushJobRequest.ts#L24-L108" }, { "kind": "response",