Open
Description
When performing an UPDATE, UPSERT, or INSERT ON CONFLICT into a table with multiple column families, if there is a multi-column check constraint on the table that involves multiple column families we might read some column families that are not modified. Under Read Committed isolation we need to take shared locks when reading these unmodified column families, to maintain the check constraint in the face of concurrent modifications. We currently do not do this, so this is disallowed under Read Committed isolation.
Jira issue: CRDB-32442
Epic CRDB-38938
Metadata
Metadata
Assignees
Labels
Type
Projects
Status