crosscluster/logical: check NOT NULL and DEFAULT value on the kv write path #134570
Labels
A-disaster-recovery
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
P-2
Issues/test failures with a fix SLA of 3 months
T-disaster-recovery
Currently the kv write path does not recheck that a replicating row abides by the destination table's DEFAULT and NOT NULL constraints. That being said, since LDR only supports single column family tables & tables with identical schema, then the replicating row already passed the identical check on the source side. So, it really isn't a big deal to skip replicating check constraints on the kv write path. We'd like to add this checks as we want the kv and sql paths to eventually converge.
Jira issue: CRDB-44147
The text was updated successfully, but these errors were encountered: