You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a changefeed is created using WITH mvcc_timestamp and Avro format, the mvcc_timestamp never gets emitted in the message. Using WITH updated works for emitting the updated timestamp, but mvcc_timestamp is required to accurately include the timestamp during an initial scan.
Insert a row into the movr.users table. Notice that the changefeed message does not have the mvcc_timestamp field.
Expected behavior
The mvcc_timestamp field is included, similar to how it is included when using json format.
Environment:
CockroachDB version 23.2.2
Server OS: Linux
Client app: cockroach sql
Additional context
The only other option is to use the updated field, which does not accurately reflect the mvcc_timestamp during initial scan or backfill.
Describe the problem
When a changefeed is created using
WITH mvcc_timestamp
and Avro format, the mvcc_timestamp never gets emitted in the message. UsingWITH updated
works for emitting the updated timestamp, butmvcc_timestamp
is required to accurately include the timestamp during an initial scan.To Reproduce
Setup a confluent schema registry.
Run
cockroach demo
.Run the following sinkless changefeed:
Insert a row into the
movr.users
table. Notice that the changefeed message does not have themvcc_timestamp
field.Expected behavior
The
mvcc_timestamp
field is included, similar to how it is included when usingjson
format.Environment:
cockroach sql
Additional context
The only other option is to use the
updated
field, which does not accurately reflect themvcc_timestamp
during initial scan or backfill.Jira issue: CRDB-38190
The text was updated successfully, but these errors were encountered: