Review selected Cloudera Migration Assistant issues resolved in 4.1.0 for this release.
Cloudera Migration Assistant 4.1.0
- CMA-4482: Spark migration failure caused by missing runAirflow build tool
- 4.1.0
The code-migration build agent could call a
runAirflow tool that was not implemented, which failed Spark
migrations. The agent prompt no longer references that tool.
- CMA-4381: External agent gRPC connection drops silently after idle period
- 4.1.0
After a long idle period, an external CMA Agent could lose its gRPC session to the CMA Master without a clear error. Connection handling
was improved so idle sessions are detected and re-established.
- CMA-4380: Unable to find transition config
- 4.1.0
Startup could fail when the transition configuration
directory was missing from the deployment layout. The server now falls back to transition
definitions on the classpath when the directory is absent.
- CMA-4251: Execution Details Collections empty for CDE-to-Git plans
- 4.1.0
After you created a new version of a Cloudera Data Engineering-to-Git plan, the Execution Details Collections view
could stay empty because plan label metadata was not copied to the new version. Label
versions are now copied when a plan version is created.
- CMA-4147: Migration Plan Title cannot be cleared
- 4.1.0
After you set a migration plan title, the UI did not
let you clear the field back to empty. You can now remove the title when you need to
reset it.
- CMA-4095: Git scan doesn't work with enterprise github
- 4.1.0
Git scans against some GitHub Enterprise Server
instances failed because repository URLs and API endpoints were not resolved correctly.
Scanning now supports common enterprise GitHub deployment patterns.
- CMA-4090: Git scan failed with NoSuchFieldError: SNAKE_CASE
- 4.1.0
Git scans could fail with a
NoSuchFieldError for SNAKE_CASE because of an
incompatible Jackson dependency on the agent classpath. Dependency alignment was
corrected so Git scanning completes successfully.
- CMA-3980: Migration unexpectedly creates build files in the git repo root
- 4.1.0
Some code migrations wrote build artifacts at the root
of the target Git repository instead of under the expected project directories. Output
paths were corrected so build files land in the intended locations.
- CMA-3979: Git push does not happen until the last iteration is completed
- 4.1.0
During iterative Git migrations, changes were not pushed
to the remote repository until the final iteration finished, which delayed verification on
the target. Push timing was adjusted so intermediate results are available when
appropriate.
