DanielLeens commented on issue #10203:
URL: https://github.com/apache/seatunnel/issues/10203#issuecomment-5086320730

   Thanks for picking this up, @mzw111. I have assigned the issue to you.
   
   Please start with a short design note before writing the full 
implementation. The most important points to make explicit are:
   1. how and when new matching tables are discovered in a running job,
   2. how checkpoint / restore semantics stay correct after a new table is 
admitted,
   3. how split ownership is tracked so dynamic discovery does not create 
ambiguous replay behavior,
   4. and whether the first version should stay default-off behind an explicit 
config.
   
   Once those boundaries are written down, a Draft PR will be a good next step.


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