All Products
Search

This Product

    Dataphin:configure logical table data latency

    Document Center

    Dataphin:configure logical table data latency

    Last Updated:Feb 12, 2026

    When you configure data latency for a dimension table or logical fact table, the system automatically re-runs all data for the associated logical tables within the maximum latency period. This topic describes how to configure data latency for dimension and logical fact tables.

    Limits

    • You can configure data latency only if the current tenant engine is MaxCompute, E-MapReduce3.x, E-MapReduce5.x, CDH 5.X, CDH 6.X, Cloudera Data Platform, FusionInsight 8.X, AsiaInfo DP 5.3, or Amazon EMR, the data timeliness of the logical fact table is daily timeliness (offline T+1), and an event time field is configured in the logical table.

    • You cannot enable delayed data processing if the logical table does not have an event time field or a primary key configured.

    • After you enable data latency, you cannot enable custom materialization for the same logical table.

    Procedure

    1. In the top menu bar of the Dataphin homepage, choose Development > Data Development.

    2. On the Development page, select a Project. In Dev-Prod mode, also select an Environment.

    3. In the navigation pane on the left, choose Standard Modeling > Logical Dimension Table or Logical Fact Table. Then, select the target logical table from the logical model subtree on the right.

    4. On the target logical table tab, click Scheduling Configuration to open the Scheduling Configuration panel.

    5. In the Scan Configuration panel, enable Data Latency for the logical table. After enabling this setting, the system automatically re-runs all data for the logical table within the maximum latency period (1 to 15 days). This feature consumes additional computing resources and may cause output delays.

      Note

      • You cannot enable delayed data processing if the logical table does not have an event time field or a primary key configured, or if custom materialization is enabled for the logical table.

      • Delayed data processing automatically re-runs only the logical fact table within the configured latency period. Downstream tables are not re-run automatically.

      • If you delete the primary key from a logical table that has data latency enabled, data latency is automatically disabled.

    6. Click OK.

    What to do next

    After configuring data latency for the logical table, configure its scheduling properties. For more information, see Configure Logical Table Scheduling Properties.