Skip to main content

Import into a Hop project

For a real migration, import into the Hop project the pipelines will live in, rather than into a loose folder.

1. Import​

<hop>/hop-import.sh -t talend -i <project-folder> --project <hop-project> \
  --pipeline-run-configuration <pipeline-run-config> \
  --workflow-run-configuration <workflow-run-config>
  • --project writes into the Hop project's home folder instead of -o. It needs the Hop projects plugin, which a standard Hop installation has.
  • The run configurations are set on every pipeline and workflow action and executor the import generates. Without them, local is used, and created if the project does not have one; an existing local is left as it is.
  • --skip-existing is on by default, so importing again does not overwrite a pipeline you have already finished by hand. Use --no-skip-existing to overwrite.

In Hop GUI, File → Import from Talend… offers the same options on its Target and Metadata tabs.

2. Create the environments​

The import writes one file per Talend context under environments/ in the output folder, for example environments/production-config.json. Register each as a Hop environment of the project:

<hop>/hop-conf.sh -ec -e production -ep <hop-project> -eg <path>/environments/production-config.json

Run with that environment (-e production on hop-run, or the environment selector in Hop GUI) and the pipelines get the context's values.

3. Add passwords​

Talend passwords cannot be read from the export. See Finish connections and passwords.