Skip to content

Commit 079066f

Browse files
committed
Edit the upgrade transform API
1 parent e2eb9af commit 079066f

File tree

3 files changed

+19
-11
lines changed

3 files changed

+19
-11
lines changed

output/openapi/elasticsearch-openapi.json

Lines changed: 2 additions & 2 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

output/schema/schema.json

Lines changed: 3 additions & 3 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

specification/transform/upgrade_transforms/UpgradeTransformsRequest.ts

Lines changed: 14 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -21,12 +21,20 @@ import { RequestBase } from '@_types/Base'
2121
import { Duration } from '@_types/Time'
2222

2323
/**
24-
* Upgrades all transforms.
25-
* This API identifies transforms that have a legacy configuration format and upgrades them to the latest version. It
26-
* also cleans up the internal data structures that store the transform state and checkpoints. The upgrade does not
27-
* affect the source and destination indices. The upgrade also does not affect the roles that transforms use when
28-
* Elasticsearch security features are enabled; the role used to read source data and write to the destination index
29-
* remains unchanged.
24+
* Upgrade all transforms.
25+
* Transforms are compatible across minor versions and between supported major versions.
26+
* However, over time, the format of transform configuration information may change.
27+
* This API identifies transforms that have a legacy configuration format and upgrades them to the latest version.
28+
* It also cleans up the internal data structures that store the transform state and checkpoints.
29+
* The upgrade does not affect the source and destination indices.
30+
* The upgrade also does not affect the roles that transforms use when Elasticsearch security features are enabled; the role used to read source data and write to the destination index remains unchanged.
31+
*
32+
* If a transform upgrade step fails, the upgrade stops and an error is returned about the underlying issue.
33+
* Resolve the issue then re-run the process again.
34+
* A summary is returned when the upgrade is finished.
35+
*
36+
* To ensure continuous transforms remain running during a major version upgrade of the cluster – for example, from 7.16 to 8.0 – it is recommended to upgrade transforms before upgrading the cluster.
37+
* You may want to perform a recent cluster backup prior to the upgrade.
3038
* @rest_spec_name transform.upgrade_transforms
3139
* @availability stack since=7.16.0 stability=stable
3240
* @availability serverless stability=stable visibility=private

0 commit comments

Comments
 (0)