Skip to content

Commit

Permalink
[Transform][DOCS] remove 7.x related limitations (elastic#78975)
Browse files Browse the repository at this point in the history
remove 7.x related limitations from limitations documentation for 8.x
  • Loading branch information
Hendrik Muhs authored Oct 12, 2021
1 parent 68bc320 commit df32157
Showing 1 changed file with 0 additions and 18 deletions.
18 changes: 0 additions & 18 deletions docs/reference/transform/limitations.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -77,15 +77,6 @@ occur at `frequency` interval.
[[transform-operational-limitations]]
== Operational limitations

[discrete]
[[transform-rolling-upgrade-limitation]]
=== {transforms-cap} reassignment suspended during a rolling upgrade from 7.2 and 7.3

If your cluster contains mixed version nodes, for example during a rolling
upgrade from 7.2 or 7.3 to a newer version, {transforms} whose nodes are stopped
will not be reassigned until the upgrade is complete. After the upgrade is done,
{transforms} resume automatically; no action is required.

[discrete]
[[transform-aggresponse-limitations]]
=== Aggregation responses may be incompatible with destination index mappings
Expand Down Expand Up @@ -281,15 +272,6 @@ destination indices and other saved objects in {kib} and to see only the objects
that belong to your space. However, this limited scope does not apply to
{transforms}; they are visible in all spaces.

[discrete]
[[transform-rolling-upgrade-ui-limitation]]
=== {transforms-cap} UI will not work during a rolling upgrade from 7.2

If your cluster contains mixed version nodes, for example during a rolling
upgrade from 7.2 to a newer version, and {transforms} have been created in 7.2,
the {transforms} UI (earler {dataframe} UI) will not work. Please wait until all
nodes have been upgraded to the newer version before using the {transforms} UI.

[discrete]
[[transform-kibana-limitations]]
=== Up to 1,000 {transforms} are listed in {kib}
Expand Down

0 comments on commit df32157

Please sign in to comment.