Consider the following table schema and sequence of changefeed messages:
create table t (pk int primary key using hash, a int not null, b int not null not visible);
upsert into t (pk,a,b) values (2,4,4);
upsert into t (pk,a,b) values (2,5,5);
delete from t where pk=2;
The before block always emits the previous row value and not the requested projection. This is problematic in use cases where a projected value is required to successfully process a deletion.
Also note that the not-visible b column is present in the before value.
Consider the following table schema and sequence of changefeed messages:
The
before
block always emits the previous row value and not the requested projection. This is problematic in use cases where a projected value is required to successfully process a deletion.Also note that the not-visible
b
column is present in thebefore
value.Jira issue: CRDB-42726