DanielLeens commented on PR #11550: URL: https://github.com/apache/seatunnel/pull/11550#issuecomment-5178099581
Following up after @SEZ9's `LGTM, can merge`. I have rechecked this head and I agree with their conclusion — no source-level blocker from my side either, so we are aligned. The restore-path pruning is scoped to the captured-table set and does not change behavior for jobs whose table set is unchanged, which is the property I care most about on a restore path. The remaining gate is CI: the required `Build` check on this head is currently failing. Before you spend time on it, worth noting that the branch is well behind `dev`, so the failing lanes may not be attributable to this diff at all. My suggestion is to sync with the latest `dev` and rerun first — not as a routine request, but because a signal from a refreshed base is the only one that will tell you anything useful here. If the same lanes are still red afterwards, please paste the fresh failing job links and I will help narrow them down. With two reviewers now agreeing on the source, this needs a committer's approval once CI is green. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
