Behavioral changes in Cloudera Migration Assistant 4.0

Behavioral changes denote a marked change in behavior from the previously released version to this version of Cloudera Migration Assistant. This release separates versioned migration plans from executions, aligns the product experience with that model, and ends support for certain deployment paths.

Cloudera Migration Assistant 4.0.0

Summary: Migration plans and executions are distinct: Previous behavior:
Migrations were modeled in ways that did not consistently separate the migration plan from individual runs of that work.; New behavior:
Migration plans and executions are separate concepts. Plans are versioned and can be run multiple times.
Summary: Express Migration workflow replaced by plan-based migration: Previous behavior:
You could follow an Express Migration path alongside other migration flows.; New behavior:
You must use the standard plan-based migration flow. For removal details, see Deprecations.
Summary: Public cloud migration removed: Previous behavior:
Public cloud migration paths were available in prior releases.; New behavior:
Public cloud migration support is removed in this release. It will be reintroduced in a future release with the new architecture.
Summary: Air-gapped deployment mode removed: Previous behavior:
Air-gapped deployment mode was supported for restricted networks.; New behavior:
Air-gapped deployment mode is no longer supported.