Dataphin:Configure upstream dependencies for a logical table

Procedure

1. In the top menu bar of the Dataphin home page, choose Develop > Data Studio.

2. On the Develop page, select a Project from the top menu bar. If you are in Dev-Prod mode, you must also select an Environment.

3. In the navigation pane on the left, choose Standardized Modeling > Logical Dimension Table or Logical Fact Table. In the Logical Table list, click the name of the target logical table.

4. On the Logical Table tab, click Scheduling Configuration in the menu bar to open the Scheduling Configuration panel.

5. In the Scheduling Properties area, configure the upstream dependencies for the logical table.

   1. Upstream Dependency

      • Auto Parse

        • Click Auto Parse. Dataphin automatically parses the calculation logic of the logical table to identify its upstream nodes and output tables. After parsing is complete, all identified dependency tables are added to the upstream dependency list. You can view the details of the parsed dependency tables, or edit or delete them.

        Note

        • If an input table identified by auto-parsing has multiple output nodes, all these nodes are set as upstream dependencies by default.

        • The dependency cycle for all parsed dependency tables is set to Current Cycle by default.

      • Add Root Node

        If the node has no upstream dependencies, click Add Root Node to set a root node as the upstream dependency.

        Note

        During init, each tenant or enterprise is assigned a virtual root node whose name starts with virtual_root_node.

      • Add Previous Cycle of This Node

        This makes the node's current run dependent on the successful completion of its previous run, such as the previous day or n hours ago.

      • Add Dependency

        If Auto Parse fails to parse the scheduling dependencies, or if the upstream dependency configuration generated by Auto Parse is unsuitable for your application, you can click +Add Dependency to manually add upstream dependencies for the node.

        Important

        When you add a dependency, the Dependency Cycle and Dependency Policy are automatically set to the recommended default values. To make changes, click the edit icon in the dependency list to modify these settings for an individual dependency.

        • Dependency Cycle: The time range during which the upstream node instance is scheduled to run. Typically, this is the current day, which covers the interval [00:00–24:00).

        • Dependency Policy: Specifies which instance to depend on if multiple instances exist within a dependency cycle. If only one instance exists, any policy option is valid. Only relative path policies are supported to ensure compatibility with potential changes to upstream scheduling.

        For more information about the default policies for cross-cycle dependencies, see Appendix: Default policies for cross-cycle dependencies.

        • Add Dependency - Physical Node

          Select one or more physical nodes from the node list. You can search for and filter physical table nodes by This Project, Project, Node Type, Node Name keyword, or Output Table Name keyword.

        • Add Dependency - Logical Table Node

          Select one or more logical table nodes from the node list. You can search for and filter logical table nodes by Logical Table Type, Module, and Logical Table Name.

          To depend on specific fields in a logical table instead of the entire table, you can click the icon in the Dependency Fields column of the node list to view the available fields in the logical table. You can then select the required fields.

        • Add Dependency - Cross-tenant Collaboration Node

          Select one or more cross-tenant collaboration nodes from the node list. You can search for and filter these nodes by Tenant, Node Type, and Node Name keyword.

   2. Outputs of This Node

      The system automatically generates an output name for the node. To add more output names, click Auto-generate Output Name.

      Important

      The system uses output names to build the scheduling dependency graph. Output names are generated automatically. Manual changes are not recommended.

6. Click OK to save the scheduling dependency configuration.

Appendix: Default policies for cross-cycle dependencies