Manage Offline Computing Tasks

Procedure

1. On the Dataphin home page, from the top menu bar, select Development > Data Development.

2. On the Development page, from the top menu bar, select Project. If you are in Dev-Prod mode, select an environment.

3. In the left navigation pane, select Data Processing > Compute Tasks.

4. Click Computing Task List at the bottom of the list to open the Offline Computing Task List tab.

5. On the Offline Computing Task List tab, perform the following operations. The table below describes each operation.

   Operation	Description
   Filter	You can filter offline computing tasks by entering a computing task ID or computing task name. This is useful for quickly finding a specific auto triggered task when you know its ID or name. You can also select Developed By Me to filter the tasks. For more filter options, click Filter to view additional criteria. The filter criteria are as follows. Task Type: Filter by task type supported by the current compute engine. Scheduling Method: Filter by the scheduling method of offline computing tasks. Options include Normal, Dry-Run, Paused, and One-Time Task. For more information, see Scheduling Method Description. Development Owner: Filter by the development owner of the task. Last Submission Status: Filter by the submission status of the last submission. Includes Submitting, Submission Succeeded, Submission Failed, and Succeeded With Warning. Output Table: Filter by the output table name of offline computing tasks. Created At: Filter by the creation time of offline computing tasks. Referenced Computing Template: Filter by the computing template referenced by offline computing tasks. Task Status: Filter by the development status of computing tasks. Includes Draft, Developing, Submitted, and Submitting. Recurrence: Supports filtering by 6 scheduling cycles: Minute, Hour, Day, Week, Month, and Year. Operation Owner: Filter by the O&M owner of offline computing tasks. Published: Filter by whether offline computing tasks are published. Conditional Scheduling: Filter by whether conditional scheduling for offline computing tasks is enabled or disabled. Last Modified Time: Filter by the last modified time of offline computing tasks. Includes the last 3 days, last 7 days, last month, or a custom time range. Tag: Select one or more task tag values to filter. Location Folder: Filter by the task's direct folder. This does not include tasks in subdirectories of the selected folder. If you select Include tasks in subdirectories, the filter results include all tasks in the selected folder and its subdirectories. Click Reset to quickly clear all filter conditions and restore system defaults.
   View Batch Operation Records	Click View Batch Operation Records. In the Batch Operation Records panel, click the Submit or Other Operations tab to view the batch operation records for the corresponding operation.
   Create Computing Task	Click +Create Computing Task. Select the type of offline computing task to create, then create it.
   List Header Configuration	Click the icon above the list to configure the list header. This lets you select which fields to display in the list.
   Refresh	Click the icon above the list to refresh the current offline computing task list.
   Open Task	Click the icon in the Actions column for the target offline computing task to open its tab. In this tab, you can perform operations such as editing and configuration.
   Acquire Lock	Acquire and lock the edit lock for the current offline computing task. Single operation: You can click the icon in the Actions column of the target offline computing task to obtain the edit lock for the current offline computing task. Batch operation: Select multiple tasks in the offline computing task list, or select the check box before Select at the bottom of the page to select all. Click Batch Acquire Lock at the bottom of the page to acquire and lock the edit locks for multiple offline computing tasks. Note The offline computing task list tab does not support releasing locks. Release locks on the corresponding offline computing task tab.
   Locate Folder	Click the icon in the Actions column of the target offline computing node to locate the node in the task tree on the left.
   Change Development Owner	Change the development owner of the current offline computing task to another user. Single operation: Click the icon in the Actions column of the target offline computing task, and select Transfer To Development Owner. In the Change Development Owner dialog box, select the target user. Then click OK. Batch operation: Select multiple tasks in the offline computing task list, or select the check box before Select at the bottom of the page to select all. Click the icon at the bottom of the page, then select Batch Change Development Owner. In the Batch Change Development Owner dialog box, select the target user. Then click OK.
   Go to O&M	Go to the Operation Center to manage the specified computing task. Click the icon in the Actions column of the target offline computing task, select Go To O&M, and navigate to the task O&M page. For more information, see View and manage script tasks, View and manage one-time tasks.
   Modify Referenced Template Version	Offline tasks that reference a computing template support modifying the version of the referenced computing template. Single operation: Click the icon in the Actions column for the target offline computing node and select Modify Referenced Template Version. In the Modify Referenced Template Version dialog box, select the Template Version. Then click OK. Batch operation: In the offline computing task list, select multiple computing tasks that use the same computing template. Click the icon at the bottom of the page, then select Batch Modify Referenced Template Version. In the Batch Modify Referenced Template Version dialog box, select the Template Version. Then click OK. Note To modify the referenced template version, you must submit and publish the node before the modification takes effect.
   Unpublish	Supports taking published compute nodes offline. Single Operation: Click the icon in the Actions column of the target offline computing task, and select Unpublish. In the Unpublish dialog box, enter a remark (up to 128 characters). Then click OK and Submit. Batch Operations: Select multiple tasks in the offline computing task list, or select the check box before Select at the bottom of the page to select all. Click the icon at the bottom of the page, then select Batch Unpublish. In the Batch Unpublish dialog box, enter a remark (up to 128 characters). Then click OK and Submit. Note If the current task has cross-tenant downstream tasks, unpublishing is not supported. If the offline computing task has downstream dependent nodes, the unpublish operation will not take effect. After successful unpublish submission, go to the pending publish list to publish the object to the production environment.
   Unpublish and Delete	You can unpublish and delete published compute tasks. Single operation: Click the icon in the Actions column of the target offline computing task, and select Unpublish And Delete. In the Unpublish and Delete dialog box, enter a remark (up to 128 characters). Then click OK and Submit. Batch operation: Select multiple tasks in the offline computing task list, or select the check box before Select at the bottom of the page to select all. Click the icon at the bottom of the page, then select Batch Unpublish and Delete. In the Batch Unpublish and Delete dialog box, enter a remark (up to 128 characters). Then click OK and Submit. Note If the offline computing task has downstream dependent nodes, the unpublish and delete operation will not take effect. Tasks published to production are only unpublished, not deleted. After successful unpublish and delete submission, go to the pending publish list to publish the object to the production environment. If the current tenant does not have the R&D Platform Settings > Offline and Delete > Development Environment Allows Deletion of Published Objects configuration enabled, the offline and delete operation is not supported for published development objects in a Dev-Prod project.
   Delete	Supports deleting compute tasks that are in Draft status. Click the icon in the Actions column of the target compute task, select Delete, enter Remarks in the Delete dialog box, and then click OK And Submit. Note If the R&D Platform Settings > Unpublish and Delete > Allow deletion of published objects in the development environment configuration is not enabled for the current tenant, you cannot delete a development object in the draft state from a Dev-prod project if the object has a corresponding production object.
   Batch Modify Tags	Replace or append tags for multiple offline computing tasks. Select multiple tasks in the offline computing task list, or select the check box before Select at the bottom of the page to select all. Click the icon at the bottom of the page, then select Batch Modify Tags. In the Batch Modify Tags dialog box, select the Modification Type and Tag. If you select Replace as the modification type, the system clears existing tags for the selected tasks and applies the new tags. If you select Append, the system keeps existing tags for the selected tasks and adds the new tags. Click OK to modify the tags.
   Batch Move	Move multiple offline computing tasks to other folders simultaneously. Select multiple tasks in the offline computing task list, or select the check box before Select at the bottom of the page to select all. Click the icon at the bottom of the page, then select Batch Move. In the New Folder dialog box, enter the folder Name and select the folder Directory. Folder names can be up to 256 characters long. They cannot contain vertical bars (|), forward slashes (/), backslashes (\), colons (:), question marks (?), angle brackets (<>), asterisks (*), or double quotation marks ("). Click OK to complete the batch move.
   Batch Scheduling Configuration	Important Batch Scheduling Configuration applies only to auto triggered tasks. After batch configuration, the existing schedule property configurations of the selected auto triggered tasks will be overwritten. Exercise caution. If conditional scheduling is already configured for the selected auto triggered tasks, changing the schedule type to dry-run or pause during batch configuration will disable conditional scheduling in bulk. Modify scheduling configuration information for multiple offline computing tasks simultaneously. You can batch modify basic scheduling or conditional scheduling separately. Batch Modify Basic Scheduling: When you enable Batch Modify Basic Scheduling, you can batch modify the configuration method, scheduling type, and scheduling cycle of the selected nodes. For detailed configuration instructions, see Configure offline pipeline scheduling configuration. Batch modify conditional scheduling: This feature is disabled by default. After you enable this feature, you can batch modify the Configuration method and Scheduling conditions for the conditional scheduling of selected nodes. For details about the configuration, see Conditional scheduling. Note Conditional scheduling applies only to tasks whose scheduling method is Normal scheduling. When the configuration method is set to Custom Settings, cross-node parameters are not supported as conditions. Start Time applies only to nodes whose scheduling cycle is Day, Week, or Month.
   Batch Dependency Configuration	Configure dependency information for multiple offline computing tasks simultaneously. Select multiple tasks in the offline computing task list, or select the check box before Select at the bottom of the page to select all. Click the icon at the bottom of the page, then select Batch Dependency Configuration. In the Batch Dependency Configuration dialog box, add, delete, or edit dependencies. If multiple upstream dependencies exist, you can click Add Dependency, and select Script Task, Logical Table Node, or Cross-tenant Dependency to add them. For more information about scheduling dependencies, see Configure Scheduling Dependencies for Offline Tasks. Click OK to complete the batch dependency configuration. Note The list in the Batch Dependency Configuration dialog box displays only the manually added upstream dependencies that are common to the selected nodes (meaning they have the same dependent object and dependency settings). Any additions, deletions, or edits will be applied to all selected nodes. Adding cross-tenant dependencies is supported only if the current tenant has enabled cross-tenant dependencies.
   Batch Parameter Configuration	Configure parameters for multiple offline computing tasks simultaneously. To configure multiple parameters, click +Add Parameter to add them. Select multiple tasks in the offline computing task list, or select the check box before Select at the bottom of the page to select all. Click the icon at the bottom of the page, then select Batch Parameter Configuration. In the Batch Parameter Settings dialog box, configure the parameters. To configure multiple parameters, you can click +Add Parameter. For details about runtime parameters, see Configure runtime parameters for offline tasks. Click OK to complete the batch parameter configuration. Note The settable parameters are a collection of local variables for the selected tasks. The system overwrites the values of these parameters for all selected tasks. If you set the parameter paramA=valueA but task `taskA` does not contain the `paramA` parameter, `taskA` is skipped. If the task contains the parameter, its `paramA` parameter is set to `valueA`. You cannot batch set the values of workspace name variables or global variables.
   Batch Run Configuration	Configure run configurations for multiple offline computing tasks simultaneously. Select multiple tasks in the offline computing task list, or select the check box before Select at the bottom of the page to select all. Click the icon at the bottom of the page, then select Batch Run Configuration. In the Batch Run Configuration dialog box, configure Run Timeout and Auto Rerun Upon Failure. For details about run configurations, see Compute Node Run Configuration. Click OK to complete the batch run configuration. Important After a batch configuration, the existing running configurations of the selected nodes will be overwritten. Please proceed with caution.
   Modify Project Ownership	Modify the project ownership for offline computing tasks. Single operation: In the directory tree on the left of the offline computing task, click the icon after the target offline computing task, then select Modify Project Ownership. In the Modify Project Ownership dialog box, select the Target Project, Folder, Template (if any), and enter the Task Name. Target Project: Select a project under the current tenant where the current user has development permissions, and which has the same mode as the current project (either both Basic mode or both Dev-Prod mode) and the same engine type. Search by project name keyword. Folder: Select a folder in the offline computing task directory tree under the target project. The default is / (root directory). Template: If the current task references an offline computing template, and a computing template of the same task type exists under the target project, select the computing template and its version for the current task. Task Name: The task name after migration to the target project. The default is the current task name. If a task with the same name exists in the target project, modify the task name. Then click OK. Batch operation: Select multiple tasks in the offline computing task list, or select the check box before Select at the bottom of the page to select all. Click the icon at the bottom of the page, then select Modify Project Ownership. In the Modify Project Ownership dialog box, select the Target Project, Folder, and Template. Target Project: Select a project under the current tenant where the current user has development permissions, and which has the same mode as the current project (either both Basic mode or both Dev-Prod mode) and the same engine type. Search by project name keyword. Folder: Select a folder in the offline computing task directory tree under the target project. The default is / (root directory). Template: If the selected tasks are of the same type, and some tasks reference an offline computing template, select a computing template of the same task type and its version under the target project for the selected tasks. Click OK to complete modifying the project. After modifying the task's project ownership: The task ID, code, and upstream and downstream dependencies remain unchanged. The project ownership of the current task's output table (if any) changes synchronously, and downstream tasks referencing this table also change synchronously. Go to the target project to submit and publish the task. Historical versions of the current task in the original project are retained, but rolling back to versions from the pre-migration project is not supported. If batch modification of project ownership fails, view the failure logs in the batch operation records.