Whether the raw change data may contain identical insert/delete carry-over pairs produced by copy-on-write file rewrites.

When true and the CDC query's deduplicationMode is not none, Spark will remove carry-over pairs from the raw change data. If false, the connector guarantees that no carry-over pairs are present in the raw change data and Spark will skip carry-over removal entirely.

Whether the raw change data may contain multiple intermediate states per row identity within the requested changelog range (across all commit versions in the range).

When true and the CDC query's deduplicationMode is netChanges, Spark will collapse multiple changes per row identity into the net effect. If false, the connector guarantees at most one change per row identity across the entire changelog range, and Spark will skip net change computation.

Returns a new ScanBuilder for reading the change data.

Whether updates in the raw change data are represented as delete+insert pairs rather than fully materialized update_preimage and update_postimage entries.

When true and the CDC query's computeUpdates option is enabled, Spark will derive update_preimage/update_postimage from insert/delete pairs in the raw change data. If false, the connector guarantees that update pre/post-images are already present in the raw change data.

Returns the columns that uniquely identify a row, used for carry-over removal, update detection, and net change computation.

The default implementation throws UnsupportedOperationException. Connectors must override this method when any of #containsCarryoverRows(), #representsUpdateAsDeleteAndInsert(), or #containsIntermediateChanges() returns true. Each referenced column must be non-nullable.

Returns the column that holds the row version — the commit version at which the row's content was last modified. The row version has these properties:

• Assigned the current commit version when the row is initially inserted.
• Bumped to the current commit version when the row's content is updated.
• Preserved when the row is rewritten by a copy-on-write operation without a content change — it is NOT bumped to the current commit version.

The row version is distinct from _commit_version. _commit_version identifies the commit that emitted this change row; the row version identifies the commit that last wrote the row's content. For a delete+insert pair produced within a single commit, both halves share the same row version if the pair is a copy-on-write carry-over, and have different row versions (old on the delete, new on the insert) if the pair is a true update.

Spark uses the row version to distinguish copy-on-write carry-over from update without scanning data columns, for both carry-over removal and update detection.

The default implementation throws UnsupportedOperationException. Connectors must override this method when #containsCarryoverRows() or #representsUpdateAsDeleteAndInsert() returns true. The referenced column must be non-nullable.