Skip to main content

Check Replication Consistency

After replication, you can run a consistency check to verify that the target catalog matches the source. This compares table states across catalogs and reports any differences.


Run a Consistency Check

  1. Open a replication from Iceberg > Replications
  2. Click the Consistency tab
  3. Click Start Consistency Check

The check runs asynchronously. The page updates as the check progresses.


Consistency States

StateMeaning
Not StartedNo check has been run for this replication
In ProgressThe check is currently comparing source and target
ConsistentAll replicated tables match between source and target
InconsistentDifferences were detected between source and target
Check FailedThe check encountered an error and could not complete

When to Check

  • After an initial one-time replication completes
  • Periodically for continuous replications, to verify ongoing consistency
  • After recovering from an error or enforcement pause
  • When investigating suspected data drift

Interpreting Results

Consistent — the replicated tables on the target match the source at the time of the check. The status panel shows how many tables and views were verified. No action needed.

Inconsistent — one or more tables or views differ. The status panel shows the number that failed alongside the total checked, and a results table lists each item with its namespace, name, kind (table or view), pass/fail status, and the reason for any failure. Hover the reason cell to read the full text. Failures appear at the top of the list; use the search box to narrow large lists.

Common causes of inconsistency:

  • A replication was interrupted before completing
  • The source changed after a one-time replication finished
  • Storage permissions prevented some files from being copied

Review the replication's Operations tab for failed operations, then re-run the replication to bring the target up to date.

Check Failed — the check could not read from the source or target catalog. The status panel shows the underlying error message; if any tables were checked before the failure, their results appear in the table below. Check catalog connectivity and credentials, then retry.