Auto triggered node and one-time task transformation

Limits

• Only computing tasks in draft status, such as offline computing tasks, real-time computing tasks, and integration tasks, are eligible for schedule type transformation.

• Schedule type transformation is possible when the user holds the lock on the corresponding computing task.

Procedure

1. Navigate to the Dataphin home page, and click Development from the top menu bar.

2. Choose the operation to transform the schedule type for a computing task or integration task.

   Note

   Ensure that the scheduling and property configurations are saved before transformation, as unsaved changes will be lost and cannot be recovered.

   • Computing task

     1. In the top menu bar, click the Development tab and choose Project from the same menu on the Development page; note that Dev-Prod mode requires environment selection.

     2. In the left-side navigation pane, go to Data Processing > Script Task.

     3. In the list of computing tasks, click the icon next to the desired task. For draft status auto triggered nodes, select Transform To One-time Task; for draft status one-time tasks, select Transform To Auto Triggered Node.

   • Integration task

     1. In the top menu bar, click the Integration tab, then choose Project from the same menu on the Integration page. Note that in Dev-Prod mode, you must select the appropriate environment.

     2. In the left-side navigation pane, go to Integration > Batch Pipeline.

     3. In the offline integration list, click the icon next to the desired offline integration task. For draft status auto triggered nodes, select Transform To One-time Task; for draft status one-time tasks, select Transform To Auto Triggered Node.

3. In the dialog box that appears, click Confirm to finalize the schedule type transformation.

What to do next

Following the schedule type transformation, both computing and integration tasks can be submitted and published as usual, creating version records in the historical information.

• Computing task: Users have the ability to perform version comparison and rollback operations on historical data. For comprehensive information on historical versions of computing tasks, refer to managing offline task history and managing real-time task history.

  Note

  • Please note that the rollback operation is irreversible and should be approached with caution.

  • During a rollback, if the current task status is not in draft, it can only be rolled back to a version with the same schedule type. If the task is in draft status, it can be rolled back to any version.

• Integration task: Users can view or download the corresponding offline integration tasks from the historical information.