vsantonastaso commented on PR #10799:
URL: https://github.com/apache/seatunnel/pull/10799#issuecomment-4441765914

   > Hi @davidzollo, I wanted to give an update on this. I've been working 
through all the review feedback and I believe I've addressed every comment 
raised so far. The refactoring is now quite comprehensive, beyond the original 
adapter pattern and per-connector version management, I've also removed the 
patched io.debezium.relational.TableId from production code entirely, replacing 
it with a proper migration infrastructure (LegacyTableId + 
MigrationObjectInputStream) that handles backward-compatible checkpoint 
deserialization. Everything compiles and passes unit tests locally, and I've 
verified the changes across all affected connector modules.
   > 
   > Unfortunately, CI is failing again: 
https://github.com/vsantonastaso/seatunnel/actions/runs/25653417517. I've gone 
through each failure and they all appear to be unrelated to this PR, container 
infrastructure issues (SQL Server, StarRocks, TDengine containers crashing 
mid-test), a network 404 during dependency download, and the known flaky 
CoordinatorServiceTest on Windows. I'll retrigger the failed jobs once the full 
run completes.
   > 
   > That said, I feel like I've done everything I can on my own at this point. 
This is a large change touching many modules, and maybe having someone from the 
team help review, validate the approach, or even just confirm the CI failures 
are indeed unrelated would really help move this forward. Thanks
   
   @davidzollo any feedback on this?


-- 
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]

Reply via email to