SEPURI-SAI-KRISHNA commented on issue #12966: URL: https://github.com/apache/seatunnel/issues/12966#issuecomment-6463473548
@SEZ9 the follow-up is #13010. It extends `KafkaFormatIT` as agreed: a tombstone between the compatible fixture's records on a topic of its own, both `format_error_handle_way` values, and an assertion that the committed offset moved past the tombstone. It is red in CI on both JDKs, so I am reporting it here instead of adjusting the fixture. **What failed.** `testFormatCompatibleTombstoneCheck`, first iteration (`FAIL`), at the committed-offset assertion: ``` no committed offset for jdbc_source_record_tombstone_SEATUNNEL-0 ==> expected: not <null> within 1 minutes ``` The row check just before it passed: the tombstone produced no row and every real record arrived. **Why.** The source's offset commit itself failed: ``` WARN KafkaSourceReader - Failed to commit consumer offsets for checkpoint 9223372036854775807 org.apache.kafka.clients.consumer.RetriableCommitFailedException: Offset commit failed with a retriable exception. Caused by: org.apache.kafka.common.errors.CoordinatorNotAvailableException: The coordinator is not available. ``` Kafka logged `Creating topic __consumer_offsets` 100 ms before that commit. This test is the first to commit an offset in the `KafkaFormatIT` broker, so the group coordinator did not exist yet. In the same run, `KafkaIT.testSourceKafkaStartConfigWithCommitOffset` passed its committed-offset assertion on Zeta, so the commit path works once a coordinator is up. **Proposed change, test only.** Make the group coordinator available before `executeJob`, for example with a `describeConsumerGroups` call for the run's group, without committing anything. The assertion then still passes only on SeaTunnel's own commit, and the mutation bar stays as agreed. OK to push that? -- 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]
