Configure dependencies for real-time tasks to quickly identify upstream and downstream tasks during debugging.
Procedure
-
Refer to real-time mode configuration entry to access the Real-time Mode configuration page for real-time tasks.
-
In the Dependency section of the configuration panel, configure dependency details for real-time mode tasks.
Important-
Dependencies in real-time mode do not create actual scheduling dependencies.
-
In offline mode, you must configure scheduling dependencies.

Parameter
Description
Start Parsing
For SQL node tasks, click Start Parsing to parse the code. The system identifies tables in the code and matches them with output names to determine upstream dependencies of the current node.
If project variables are referenced or no project is specified, the system uses the production project name for parsing to ensure schedule stability. For example, with a development project named
onedata_dev:-
Code
select * from s_orderresults in a dependency ofonedata.s_order. -
Code
select * from ${onedata}.s_orderalso results in a dependency ofonedata.s_order. -
Code
select * from onedata.s_orderresults in a dependency ofonedata.s_order. -
Code
select * from onedata_dev.s_orderresults in a dependency ofonedata_dev.s_order.
Upstream Dependency
To add upstream nodes for task scheduling:
-
Click Manually Add Upstream.
-
In the Create New Upstream Dependency dialog box, search for dependency nodes using either method:
-
Enter the output name of the dependent node as the search keyword.
-
Type virtual to find virtual nodes. Each tenant or enterprise has a root node assigned upon initialization.
NoteNode output names are globally unique and case-insensitive.
-
-
Click Confirm Addition.
To delete a dependency, click the
icon in the Actions column.Current Node
To set output names that other nodes can use as dependencies:
-
Click Manually Add Output.
-
In the Add Current Node Output dialog box, enter the output name following a consistent naming convention, such as
project name.table name, which is case-insensitive.For example, for a development project named
onedata_dev, the recommended output name isonedata.s_order. Setting the output name toonedata_dev.s_orderwill only allow code referencingonedata_dev.s_orderto parse the upstream dependency node. -
Click Confirm Addition.
You can also manage existing output names for the current node:
-
To delete added output names, click the Actions column's
icon. -
If the node is already submitted or published and has downstream dependencies (with submitted tasks), click the Actions column's
icon to see the dependent nodes.
-
-
Click Confirm to save the dependency configuration.