changefeedccl: uri sinks, fill in record key, WITH envelope#25542
changefeedccl: uri sinks, fill in record key, WITH envelope#25542craig[bot] merged 3 commits intocockroachdb:masterfrom
Conversation
626c6e7 to
c29bfac
Compare
|
Reviewed 8 of 8 files at r1, 2 of 2 files at r2, 2 of 2 files at r3. pkg/ccl/changefeedccl/changefeed.go, line 224 at r3 (raw file):
nit: var colIDs []sometype
if cf.envelope == optEnvelopeKeyOnly {
colIDs = tableDesc.PrimaryIndex.ColumnIDs
} else {
colIDs = tableDesc.Columns
}
for ...pkg/ccl/changefeedccl/changefeed.go, line 365 at r3 (raw file):
I'm not quite sure what the "envelope" stands for, but is it intuitive that "none" corresponds to "both"? Should it just be pkg/ccl/changefeedccl/changefeed_test.go, line 80 at r3 (raw file):
Since this is new code, can we do the Right Thing™ and pass this as a testing knob instead of futzing with a global? pkg/ccl/changefeedccl/changefeed_test.go, line 97 at r3 (raw file):
Another candidate to move into a knob. Comments from Reviewable |
|
Review status: 6 of 8 files reviewed at latest revision, 4 unresolved discussions. pkg/ccl/changefeedccl/changefeed.go, line 224 at r3 (raw file): Previously, tschottdorf (Tobias Schottdorf) wrote…
Done pkg/ccl/changefeedccl/changefeed.go, line 365 at r3 (raw file): Previously, tschottdorf (Tobias Schottdorf) wrote…
yeah. "envelope" make more sense when the third value gets introduced, which is both the new and old row values. how about pkg/ccl/changefeedccl/changefeed_test.go, line 80 at r3 (raw file): Previously, tschottdorf (Tobias Schottdorf) wrote…
Sure, though I'd like to do it on another PR if that's alright. There's a bunch of other references to this that should also get updated. #25622 pkg/ccl/changefeedccl/changefeed_test.go, line 97 at r3 (raw file): Previously, tschottdorf (Tobias Schottdorf) wrote…
I think the plan is to replace this with the sql table sink that ben suggested in the rfc Comments from Reviewable |
|
Still LGTM. Reviewed 2 of 2 files at r4, 2 of 2 files at r5, 2 of 2 files at r6. pkg/ccl/changefeedccl/changefeed.go, line 365 at r3 (raw file): Previously, danhhz (Daniel Harrison) wrote…
I'm not really in the know here, but pkg/ccl/changefeedccl/changefeed_test.go, line 80 at r3 (raw file): Previously, danhhz (Daniel Harrison) wrote…
Sure, thanks! pkg/ccl/changefeedccl/changefeed_test.go, line 97 at r3 (raw file): Previously, danhhz (Daniel Harrison) wrote…
👍 that's even better Comments from Reviewable |
|
TFTR! bors r+ |
Build failed |
|
bors r=tschottdorf |
|
Could you triage the build failure? See #25616 (comment) |
|
I looked at it before rerunning, but the test timed out and failed most of the logic tests. Are we really posting that for every flake now? I haven't heard it announced anywhere |
Build failed (retrying...) |
|
flake in TestReplicaLeaseRejectUnknownRaftNodeID |
Merge conflict (retrying...) |
Currently `kafka://` is the only supported scheme. The bootstrap servers are specified via the uri host:port. The kafka `topic_prefix` is now specified via uri param. Release note: None
Release note: None
`none` is the default and emits the primary key as the record key and the full updated row as the record value. `key_only` emits the same key but leaves the value empty. Release note: None
|
Looks like the flake is #25568. I'll help @a-robinson investigate. |
|
Never mind, he already has a fix out #25625. |
|
okay lets try this again. not sure why bors thought it had a merge conflict bors r=tschottdorf |
This is just a favor I ask, since it helps me keep track of what's urgent. Most of our builds are on PR branches, not master. Also, the authors already look at the failed build anyway (or how could they be sure that they didn't introduce the problem) so it's just a small step to let the rest of the world know what went wrong as well. Ideally, of course, the bors message would contain the snippet from bors.. filed #25632. |
25542: changefeedccl: uri sinks, fill in record key, WITH envelope r=tschottdorf a=danhhz See commit messages for details 25631: storage: ensure non-expired context before each liveness update attempt r=nvanbenschoten a=nvanbenschoten Fixes #25430. Before this change, a liveness update could get stuck in an infinite loop if its context expired. This is because it would continue to retry and continue to get `errRetryLiveness` errors due to `AmbiguousResultErrors` created by `DistSender`. Release note: None Co-authored-by: Daniel Harrison <daniel.harrison@gmail.com> Co-authored-by: Nathan VanBenschoten <nvanbenschoten@gmail.com>
Build succeeded |
See commit messages for details