Importing Objects
You can import pipelines, fragments, jobs, and topologies that were exported from Control Hub.
You can also import pipelines exported from a Data Collector or Transformer that is not registered with Control Hub.
Importing Pipelines
You can import pipelines from individual pipeline files or from an archive ZIP file. Pipeline files are JSON files exported from Control Hub, Data Collector, or Transformer.
When you import a single pipeline, you can rename the pipeline during the import. When you import a set of pipelines, Control Hub imports the existing pipeline names.
When pipelines include fragments, importing pipelines also imports any fragments used in the pipelines with the existing fragment names.
If necessary, you can rename objects after the import.
- In the Navigation panel, click .
-
Click the Import icon:
.
-
Click one of the following tabs:
- Import Pipeline - Use to import an individual
pipeline.
Enter a pipeline name and commit message, and then select the JSON file to import.
- Import from Archives - Use to import one or more
pipelines from a ZIP file. Must also be used to import pipelines that use
connections.
Optionally enter a commit message to be used for all imported pipelines. If not entered, Control Hub uses the individual commit message exported with each pipeline.
Then, select the ZIP file containing the pipeline files to import.
- Import Pipeline - Use to import an individual
pipeline.
- Click Import.
Importing Fragments
You can import fragments from individual fragment files or from an archive ZIP file. Fragment files are JSON files exported from Control Hub.
When you import a single fragment, you can rename the fragment during the import. When you import a set of fragments, Control Hub uses the existing fragment names. If necessary, you can rename fragments after the import.
- In the Navigation panel, click .
-
Click the Import icon:
.
-
Click one of the following tabs:
- Import Pipeline Fragment - Use to import an
individual fragment.
Enter a fragment name and commit message, and then select the JSON file to import.
- Import from Archives - Use to import one or more
fragments from a ZIP file. Must also be used to import fragments that use
connections.
Optionally enter a commit message to be used for all imported fragments. If not entered, Control Hub uses the individual commit message exported with each fragment.
Then, select the ZIP file containing the fragment files to import.
- Import Pipeline Fragment - Use to import an
individual fragment.
- Click Import.
Importing Jobs
You import jobs and job templates from an archive ZIP file containing job files. Job files are JSON files that contain the job or job template and the dependent pipeline and fragments exported from Control Hub.
When you import a job or job template, Control Hub imports the existing names for the job, the dependent pipeline, and any fragments used by the pipeline. If necessary, you can rename objects after the import.
Importing Topologies
You import topologies from an archive ZIP file containing topology files. Topology files are JSON files that contain the topology and the dependent jobs, pipelines, and fragments exported from Control Hub.
When you import a topology, Control Hub imports the existing topology name and the existing names for all dependent jobs, pipelines, and fragments. If necessary, you can rename the objects after the import.