@@ -33,6 +33,14 @@ upgrade from 7.2 to a newer version, and {transforms} have been created in 7.2,
33
33
the {transforms} UI (earler {dataframe} UI) will not work. Please wait until all
34
34
nodes have been upgraded to the newer version before using the {transforms} UI.
35
35
36
+ [float]
37
+ [[transform-rolling-upgrade-limitation]]
38
+ ==== {transforms-cap} reassignment suspended during a rolling upgrade from 7.2 and 7.3
39
+
40
+ If your cluster contains mixed version nodes, for example during a rolling
41
+ upgrade from 7.2 or 7.3 to a newer version, {transforms} whose nodes are stopped will
42
+ not be reassigned until the upgrade is complete. After the upgrade is done, {transforms}
43
+ resume automatically; no action is required.
36
44
37
45
[float]
38
46
[[transform-datatype-limitations]]
@@ -181,9 +189,9 @@ for the {transform} checkpoint to complete.
181
189
182
190
[float]
183
191
[[transform-scheduling-limitations]]
184
- ==== {cdataframe -cap} scheduling limitations
192
+ ==== {ctransform -cap} scheduling limitations
185
193
186
- A {cdataframe } periodically checks for changes to source data. The functionality
194
+ A {ctransform } periodically checks for changes to source data. The functionality
187
195
of the scheduler is currently limited to a basic periodic timer which can be
188
196
within the `frequency` range from 1s to 1h. The default is 1m. This is designed
189
197
to run little and often. When choosing a `frequency` for this timer consider
@@ -206,7 +214,7 @@ When using the API to delete a failed {transform}, first stop it using
206
214
207
215
[float]
208
216
[[transform-availability-limitations]]
209
- ==== {cdataframes -cap} may give incorrect results if documents are not yet available to search
217
+ ==== {ctransforms -cap} may give incorrect results if documents are not yet available to search
210
218
211
219
After a document is indexed, there is a very small delay until it is available
212
220
to search.
0 commit comments