The migration report

Applies toApache Hop 2.19.0

Every import writes talend-migration-report.md into the output folder. It is built from what that import did, so it cannot claim more than the importer did.

Sections

Section	What it holds
Totals	Jobs, components, and the count per status; the number of components flagged for review
Per job	For each job: its components and how many are flagged
Most frequent source components	Each Talend component type, how often it occurs, how often it is flagged
Needs review	Every flagged component: job, component, name, status, and the reason
Scope of this report	What the statuses do and do not claim
Connections	The Hop connections created, their database type, and whether you have to set the password
Environments	The environment files written, one per Talend context, and values that differ between jobs for the same context
Appendix	How to rebuild Talend iterate loops (tForeach, tLoop, tFlowToIterate, tIterateToFlow) in Hop, when the project has them
Jobs that failed to import	Jobs that could not be parsed or converted, with the error; only when there are any

How a component's status is decided

The status starts from the component's converter, as listed in the component mapping: Automatic or Partial. What happened during the import can then lower it:

What happened	Reported as
The converter carried the settings across	AUTO (or PARTIAL, for a partial converter)
The converter fell back to a placeholder with a TODO	MANUAL
The converter threw an error; the component is a Dummy with the error in its description	UNSUPPORTED
No converter for the component; it is a Dummy that keeps its name, position and hops	UNSUPPORTED

Always flagged

Some components are flagged whatever their status, because they always need a person to look:

• every tJava, tJavaRow and tJavaFlex: code that could not be translated is listed per idiom, with its line; translated code is flagged for verification;
• tMap expressions the importer could not translate, and lookups whose join semantics differ (a Talend inner join drops unmatched rows, a Hop Stream Lookup keeps them with nulls);
• tFileList, whose per-iteration variables become row fields in Hop;
• stored procedures, and DB Row components whose reject, commit or batch settings differ.

Richer reports

An add-on that implements the importer's IImportReportProvider interface replaces this summary with its own. Nothing in the importer depends on one being installed.