Hello @analyticsnerd ,

Enabling row tracking allows us to track row-level lineage in a Delta table across multiple versions. When enabled, delta creates/exposes two hidden metadata columns which can be accessed as _metadata.row_id and _metadata.row_commit_version

Row ID, which uniquely identifies a row across multiple versions of a table, and Row Commit Version, which makes it possible to check whether two rows with the same ID in two different versions of the table represent the same version of the row.

In simple terms, think of row tracking as giving every row in your Delta table a stable primary key + last_modified_version, managed by Delta itself. That’s mainly useful whenever you want incremental, row-level propagation of changes downstream.

Example:

• Suppose you want to incrementally refresh the MV. To understand which exact base rows have changed since the last refresh, without row tracking enabled, it would be very difficult to determine.
• Also, when you have a pipeline with Meddalion architecture, you can easily determine if a specific row in the gold table came from a row (row_id X) in the bronze table,” – which helps with audits and debugging data issues.