DanielLeens commented on PR #11077: URL: https://github.com/apache/seatunnel/pull/11077#issuecomment-4703715939
Thanks for writing this out so clearly. I agree with your direction that, if shared-writer reuse is going to be supported safely, the fix likely needs to live at the `MultiTableSink` layer where writer ownership and queue isolation are decided, not only inside one sink implementation. Since there is no new code on the PR head yet, I will stop at the discussion level for this round and wait for the follow-up commit before doing another full review. Once you push the updated implementation, I will recheck the full path from writer creation through per-table queue isolation. -- 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]
