li3zhi4 commented on PR #11633:
URL: https://github.com/apache/seatunnel/pull/11633#issuecomment-5203054998

   Thanks @DanielLeens for the detailed verification and for reading the head's 
own CI log — glad the `NotSerializableException` is confirmed gone. Issue 1 is 
addressed on the new head `876a9396a1` (test-only change, per your Option A):
   
   **Issue 1 (Kafka topic-readiness race → 
`UnknownTopicOrPartitionException`):** `waitForKafkaTopicsReady` now goes 
beyond topic existence: it also asserts every partition of every topic has a 
**non-null leader** (`describeTopics(...).values()...partitions()` → 
`partition.leader() != null`) before the job is submitted. This closes the gap 
between "topic visible to the admin client's metadata view" and "the broker the 
job's own Kafka client connects to has finished assigning/propagating the 
partition leader". Since the wait runs inside the existing Awaitility loop 
(atMost 180s, poll 500ms), it retries until the leader assignment converges. No 
production code changed.
   
   Verification: `JsonDefaultValueTest` 14/14, full `seatunnel-format-json` 
module 60/60 green, `spotless:check` clean, and `KafkaJsonDefaultValueIT` e2e 
1/1 passed locally on this head. Branch is up to date with `dev`.
   


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