pg sources: subsource health status + snapshot resumption test #18782
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As part of #18769, we discovered that the cluster test
workflow_pg_snapshot_resumption
was not working as intended, so I've refactored it to ensure that the source is down (and that the failure was caused by the failpoint).I also needed to refactor how multi-output sources propagate their health statuses to the health operator––there were two issues previously:
In service of the above, I also refactored some of the way
source_reader_pipeline
handles buffering.Motivation
This PR refactors existing code.
Checklist
$T ⇔ Proto$T
mapping (possibly in a backwards-incompatible way) and therefore is tagged with aT-proto
label.