davidzollo commented on PR #11206: URL: https://github.com/apache/seatunnel/pull/11206#issuecomment-6870278972
<!-- daniel-maintenance-20261113-11206-93afd1a996b2 --> Maintenance update for `93afd1a996b26e84b8ab843d31c736aa20ae3e9c`. The conflict resolution is prepared locally. It keeps the upstream parallel flush implementation and snapshot-only restore logic alongside this PR's runtime registration and restore gate. The existing JdbcSinkWriterTest failures remain: the runtime-create fixtures use a dialect mock without schema-change support enabled. The conflict audit also found an existing blocker in the runtime create path. If registration succeeds for the first queue and then exhausts retries for a later queue under CONTINUE_OTHER_TABLES, failure handling calls removeTableWriters while the other queue workers still hold their monitors and wait for the schema-change barrier. This can leave the dispatcher and those workers waiting on each other. Defer isolation until after the barrier releases and cover a partial registration with more than one queue. A separate outstanding case is timer registration when the first flush-capable child is created at runtime. These findings come from source; no new runtime validation was run. -- 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]
