Options and exit codes
The importer runs three ways, all with the same options and defaults:
| Way | Command |
|---|---|
| Hop GUI | File → Import from Talend…: the options on the Source, Target and Metadata tabs |
hop-import | <hop>/hop-import.sh -t talend -i <input> -o <output> [options] |
| Standalone jar | java -jar importer-talend.jar [options] <input-path> <output-dir> [metadata-root], built from the repository |
Options
| Option | Default | Meaning |
|---|---|---|
-i, --input | A single .item file, or a Talend project or export folder | |
-o, --output | Where the .hpl and .hwf files are written, mirroring the input's folder layout | |
-e, --skip-existing | on | Leave target files that already exist untouched |
-p, --skip-hidden | on | Skip hidden files and folders |
-f, --skip-folders | off | Do not recurse into sub-folders |
--all-versions | off | Import every saved version of a job, not only the newest |
--project <name> | Import into this Hop project's home folder instead of --output | |
--pipeline-run-configuration <name> | local | Run configuration for generated pipeline actions and executors |
--workflow-run-configuration <name> | local | Run configuration for generated workflow actions and executors |
-m, --metadata-root <dir> | <output>/metadata | Hop metadata folder for connections and schema definitions |
-h, --help | Print the options |
Switch a default-on option off with --no-<option> (--no-skip-existing) or --<option>=false.
The metadata folder can also be set with the TALEND_IMPORTER_METADATA_ROOT environment variable or
the talend.importer.metadata.root system property; the option wins, then the variable, then the
property.
Nothing is ever written inside the Hop metadata folder by mistake: a job in a Talend folder called
metadata is written to talend-metadata/ instead.
Exit codes
| Exit code | Meaning |
|---|---|
0 | Every job converted |
1 | The import crashed, or the input path does not exist |
2 | The command line could not be parsed; the usage text is printed |
3 | The import completed, but at least one job failed to parse or convert |
A component that fails to convert does not fail its job: it becomes a placeholder.
What is read
| Talend item | Read as |
|---|---|
Jobs and joblets (process/**/*.item, talendfile:ProcessType) | Pipelines and workflows |
Context groups (context/*.item, newest version) | Hop environments |
Repository connections (metadata/connections) | Hop relational connections |
Component schemas a transform refers to, such as a delimited file's columns, are written as Hop static schema definitions in the metadata folder. Documentation, routines, SQL patterns and other item types are skipped.