Exporting and Importing Jobs

Updated on 2024-10-28 GMT+08:00

View PDF

Exporting jobs is to export the latest saved content in the development state.
After a job is imported, the content in the development state is overwritten and a new version is automatically submitted.

NOTE:

When exporting or importing jobs across time zones in DataArts Factory, you need to change the value of expressionTimeZone to the target time zone.

Exporting Jobs

Log in to the DataArts Studio console by following the instructions in Accessing the DataArts Studio Instance Console.
On the DataArts Studio console, locate a workspace and click DataArts Factory.
In the left navigation pane of DataArts Factory, choose Development > Develop Job.
Click in the job directory and select Show Check Box.
Select jobs, click , and select Export Job. In the displayed dialog box, select Export jobs only or Export jobs and their dependency scripts and resource definitions. After the export is successful, you can obtain the exported .zip file.

Figure 1 Selecting and exporting jobs
In the displayed Export Job dialog box, set Export Scope and Job Status and click OK. You can view the result in the download center.

Figure 2 Exporting jobs

Importing Jobs

This function is available only if the OBS service is available. If OBS is unavailable, jobs can be imported from the local PC.

NOTE:

The maximum size of a job file imported from OBS is 10 MB. The maximum size of a job file imported from a local PC is 1 MB. The maximum size of a job file imported from a local PC cannot be larger than 1 MB after decompression.
If the name of a job to be imported already exists in the system, ensure that the job is in the stopped state. Otherwise, the import fails.

Import one or more jobs from the job directory.

In the left navigation pane of DataArts Factory, choose Development > Develop Job.
Click > Import Job in the job directory, select the job file that has been uploaded to OBS or local directory, and rename the policy.

NOTE:

If you select Overwrite for Duplicate Name Policy but the hard lock policy is used and the script is locked by another user, the overwriting will fail. For details about soft and hard lock policies, see Configuring the Hard and Soft Lock Policy.

Figure 3 Importing jobs and their dependencies
Click Next to import the job as instructed.
NOTE:
- If a job contains a tag in the locked state, the job fails to be imported.
- When a job fails to be imported and a tag needs to be automatically generated, if the tag already exists and is locked, it will not be added to the job.
- During the import, if the data connection, DIS stream, DLI queue, or GES graph associated with the job does not exist in DataArts Factory, the system prompts you to select one again.

Parent topic: (Optional) Managing Jobs

Previous topic: Moving a Job or Job Directory

Next topic: Configuring Jobs

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot