-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
roachtest/cdc: fix cdc/bank and cdc/schemareg #42746
roachtest/cdc: fix cdc/bank and cdc/schemareg #42746
Conversation
Partial fix for cockroachdb#42690. I don't think this ever worked. The schema change backfill for the dropped column `b` results in a record for each row that was previously inserted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @danhhz and @nvanbenschoten)
pkg/cmd/roachtest/cdc.go, line 280 at r2 (raw file):
// NB: the WITH diff option was not supported until v20.1. withDiff := t.IsBuildVersion("v19.2.1")
Is this right? We're not going to backport, so wouldn't this start failing again when we release 19.2.2?
Fixes cockroachdb#42690. Fixes cockroachdb#41177. This was broken by cockroachdb#41793.
416d073
to
7044348
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 1 of 1 files at r2.
Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @danhhz and @nvanbenschoten)
pkg/cmd/roachtest/cdc.go, line 280 at r2 (raw file):
Previously, danhhz (Daniel Harrison) wrote…
Is this right? We're not going to backport, so wouldn't this start failing again when we release 19.2.2?
Nope, it's not right. I was thinking that this was the cluster version (which hasn't been bumped on master), but it's actually the build version (which has). Fixed.
TFTR! bors r+ |
Build failed (retrying...) |
42650: sql: stop observing the CommitTimestamp in TRUNCATE r=ajwerner a=ajwerner In #40581 we stopped observing the commit timestamp to write it into table descriptors. In this change I overlooked (rather forgot) about this additional place in the code where we observed the commit timestamp. As far as I can tell we don't read this field anywhere ever. Furthermore we know that the the table descriptor in question to which we are referring must be alive and equal to the provided value at the timestamp at which it was read due to serializability. In short, this minor change continues to populate the field with a sensible value and will permit TRUNCATE to be pushed. Fixes #41566. Release note (bug fix): Long running transactions which attempt to TRUNCATE can now be pushed and will commit in cases where they previously could fail or retry forever. 42746: roachtest/cdc: fix cdc/bank and cdc/schemareg r=nvanbenschoten a=nvanbenschoten Fixes #41177. Fixes #42690. These were both broken by #41793 because prior versions of crdb didn't support the `WITH diff` option. Co-authored-by: Andrew Werner <[email protected]> Co-authored-by: Nathan VanBenschoten <[email protected]>
Build succeeded |
Fixes #41177.
Fixes #42690.
These were both broken by #41793 because prior versions of crdb didn't support the
WITH diff
option.