Import DataJobs
The DataJob import function is important for BladePipe upgrade and system migration. This article describes the prerequisites and procedures of using this function.
Prerequisites
- DataJobs are imported from BladePipe 2.2.x.x or later versions (recommended). The function relies on the open API of the source cluster. Earlier community versions such as 1.0, 2.0, 2.1, 2.2, etc. don't come with an open API, so they are not supported.
- DataJobs are imported to BladePipe 4.2.1.0 or later versions.
- Only Incremental DataJobs can be imported.
Procedure
- Click DataSource > Add DataSource. Add the DataSources that is relevant to the DataJobs to be imported.
- Navigate to DataJob page, and click Advanced Features > Import DataJob.
- Fill in the relevant information.
| Items | Description |
|---|---|
| DataJob Number ID | Get the DataJob ID by clicking the  icon in the DataJob ID & Description column on the DataJob list page. By default, the IDs of the DataJobs imported to the new system are consistent with those in the original system (to make the DataJobs distinguishable), but the IDs be generated by ticking Rename DataJob ID. |
| Cluster | The cluster to which the imported DataJobs will be allocated to, the same setting as that in DataJob creation. |
| Source DataSource ID | The Source DataSource of the DataJob. Select the public/private IP address, the same setting as that in DataJob creation. |
| Target DataSource ID | The Target DataSource of the DataJob. Select the public/private IP address, the same setting as that in DataJob creation. |
| Origin Host | The address of the original BladePipe to call the open API. |
| Origin AccessKey | The AccessKey for the open API of the original BladePipe. |
| Origin SecretKey | The SecretKey for the open API of the original BladePipe. |
| Custom Code | Since BladePipe can not get the custom code package from the open API, if there is custom code for the imported DataJob, please download it from the original system and re-upload it when importing DataJob. Tips: There are some changes between the old and new versions of bladepipe-sdk, on which the custom code depends, e.g., some new properties are added to SchemaInfo, causing equals to fail and thus the processing is skipped. Therefore, before running a new DataJob, please test and validate it again to prevent data processing logic from failing. |
- Click Submit to import the DataJob.
tip
The DataJob will not start automatically after being imported, so please check the configuration and do a system switchover (and ensure position continuity).