All Products
Search

This Product

    Dataphin:configure logical table data latency

    Document Center

    Dataphin:configure logical table data latency

    Last Updated:Jun 05, 2026

    When records for a completed partition arrive after the scheduled run, those records are excluded from the output. Data latency lets the system re-run all data for a logical table within a configurable window (1 to 15 days) to capture late-arriving records.

    Limitations

    • Data latency is available only when 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 logical fact table must also have daily timeliness (offline T+1) and a configured event time field.

    • Data latency cannot be enabled if the logical table is missing an event time field or a primary key.

    • Data latency and custom materialization are mutually exclusive. Enabling one prevents enabling the other on the same logical table.

    • Only the logical fact table is re-run automatically within the latency window. Downstream tables are not re-run.

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

    Configure data latency for a logical table

    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 left navigation pane, 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, turn on Data Latency. The system re-runs all data for the logical table within the latency window (1 to 15 days). This consumes additional computing resources and may delay output.

      Note

      • Data latency requires both an event time field and a primary key on the logical table. It cannot be combined with custom materialization. See Limitations for the full list of constraints.

    6. Click OK.

    What's next

    Configure the scheduling properties for the logical table. For more information, see Configure Logical Table Scheduling Properties.