@@ -33,6 +33,14 @@ upgrade from 7.2 to a newer version, and {transforms} have been created in 7.2,
3333the {transforms} UI (earler {dataframe} UI) will not work. Please wait until all
3434nodes have been upgraded to the newer version before using the {transforms} UI.
3535
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.
3644
3745[float]
3846[[transform-datatype-limitations]]
@@ -181,9 +189,9 @@ for the {transform} checkpoint to complete.
181189
182190[float]
183191[[transform-scheduling-limitations]]
184- ==== {cdataframe -cap} scheduling limitations
192+ ==== {ctransform -cap} scheduling limitations
185193
186- A {cdataframe } periodically checks for changes to source data. The functionality
194+ A {ctransform } periodically checks for changes to source data. The functionality
187195of the scheduler is currently limited to a basic periodic timer which can be
188196within the `frequency` range from 1s to 1h. The default is 1m. This is designed
189197to 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
206214
207215[float]
208216[[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
210218
211219After a document is indexed, there is a very small delay until it is available
212220to search.
0 commit comments