Configure Logical Table Scheduling Properties - Dataphin

This topic describes the steps to configure scheduling properties for logical table tasks, which determine the scheduling rules for logical dimension tables and logical fact tables.

Procedure

Navigate to the Dataphin home page, select Development > Data Development from the top menu bar.
On the Development page, select Project from the top menu bar.
In the left-side navigation pane, choose Standard Modeling > Logical Dimension Table or Logical Fact Table. Then click on the desired logical table name in the Logical Table list.
Click Scan Configuration in the top menu bar of the logical table tab to open the Scan Configuration panel.

Within the Scan Configuration panel, set the necessary parameters in the Scheduling Properties section.

Parameter	Description
Schedule Type	Supports three types of scheduling: normal scheduling, dry-run scheduling, and skip execution. Normal Scheduling: Configures scheduling according to the time of the scheduling period and executes normally (that is, real data is run). This option is usually selected by default for tasks. Dry-run Scheduling: Configures scheduling according to the time of the scheduling period, but all executions are dry-run (that is, no real data is run). When the task is scheduled, it directly returns success without actually executing the task. This type of scheduling is usually used when a node does not need to be executed within a certain period and does not block the execution of its descendant nodes. Skip Execution: When skip execution is selected, scheduling is initiated according to the time configured in the scheduling period, but the node status is set to pause (that is, no real data is run). When the task is scheduled, the system directly returns a failure response and the descendant nodes cannot be run. This is usually used in scenarios where a task does not need to be executed temporarily but will continue to be used later.
Priority	The priority of the current logical table can be set to Medium, Low, or Lowest. When a logical table is created, the default value of the priority is obtained from the default priority in Management Center > Development Platform Settings > Node Task Related Settings. Note When the logical table is published to the production environment or submitted in the Basic environment, the priority cannot be modified during editing. It must be modified in the production environment's operations. At this time, the priority value is the latest value in the production environment.
Recurrence	The scheduling period refers to how often the logical table task is actually executed in the production environment scheduling system. After a logical table task is successfully submitted, the task scheduling will be configured according to the time attributes of the task starting from the next day after submission, generating recurring instances for automatic scheduling. It runs based on the results of upstream dependency instances and time points. Logical Table Scheduling Period includes Day, Hour, and Minute, determined by the Data Timeliness when the logical table is created. The scheduling type does not support modification. Daily Scheduling: The logical table task runs automatically once a day. When creating a logical table task with Offline T+1 Data Timeliness, the system's default period is to run once at 00:00 every day. You can click the icon to modify the start time of the schedule as needed. Hourly Scheduling: The logical table task runs once every hour. The start time of the schedule cannot be modified. Minute Scheduling: The logical table task runs once every 15 minutes. The start time of the schedule cannot be modified. Note To ensure the normal operation of downstream instances during non-specified scheduling times, the system generates instances every day and directly sets them to run successfully without actually executing any logic or occupying resources.
Scheduling Run Plan	Click Preview. The scheduling run plan displays all scheduling instances and their scheduling types for each day of a month for the current scheduling task according to the configured scheduling period and conditional scheduling. The preview date type can be selected as Data Timestamp or Run Date (Scheduling Date). If there are multiple scheduling type statuses for all instances in one day, all scheduling type statuses included are displayed by color, along with the name of each scheduling type status and the number of corresponding instances. For example, in the figure below, on the 4th of a certain month, the current scheduling task has 44 normal scheduling instances, 2 paused instances, and 12 dry-run instances. Hover the mouse over the scheduling type module of a certain day to view the detailed scheduling instance list of the current scheduling task on that day, including scheduling type, scheduling conditions, and condition names.
Conditional Scheduling	After enabling conditional scheduling, you can set multiple groups of scheduling conditions and add up to 10 scheduling conditions. The system will evaluate the conditions in order from top to bottom. Once a condition is hit, the corresponding scheduling action is executed, and all subsequent condition evaluations are stopped. If no conditions are hit, the default scheduling configuration is executed. Important Conditional scheduling is only effective when the scheduling type is Normal Scheduling. Click +add Scheduling Condition. In the Edit Conditional Scheduling dialog box, configure the relevant information for conditional scheduling. Condition Name: Supports any characters, with a length of up to 32 characters. Effective Status: Enabled by default. When disabled, this conditional scheduling will be ignored during scheduling. Meet the Following Conditions: The rule for condition judgment. When the condition is judged to be true, scheduling is performed according to the configuration information of Execute Scheduling. For configuration instructions, see Conditional Scheduling Rule Description. Execute Scheduling: Supports custom and follow scheduling properties: Custom: When the condition is judged to be true, scheduling is run according to the configured Scheduling Type. Follow Scheduling Properties: Consistent with the scheduling policy in scheduling properties, equivalent to the scheduling settings when conditional scheduling is disabled. Scheduling Type: For configuration instructions, see the above Scheduling Type. Start Time: The start time for the logical table task to begin running. When the scheduling type of the logical table task is Normal Scheduling and Daily Scheduling, the start time defaults to 00:00 and can be modified. Click OK. After completing the conditional scheduling settings, click Preview Scheduling Run Plan to view the dates hit by conditional scheduling in the calendar. Important After modifying the conditional scheduling settings, submitting and publishing to the production environment will take effect in real-time for instances that are in the Not Running status at the time of publication. It will not take effect for instances that have entered the Waiting for Run Time status. When using cross-node parameter judgment types in conditional scheduling, possible parameter values must be provided for preview.

To finalize the configuration, click Save.