MartijnVisser opened a new pull request, #302:
URL: https://github.com/apache/flink-connector-kafka/pull/302

   Backport of FLINK-39699 (PR #254) and FLINK-39723 (PR #261) from `main` to 
`v5.0`.
   
   ## Why
   
   The weekly connector CI on `v5.0` (Flink 2.1.x and 2.2.x) keeps failing on 
tests that were stabilized on `main` but never backported:
   
   - 
`KafkaWriterFaultToleranceITCase.testFlush/testCloseExceptionWhenKafkaUnavailable`:
 "Expecting actual not to be null" (2026-08-02, 2026-08-09).
   - `KafkaSinkITCase`: "Expecting Optional to contain a value but it was 
empty" from `getCheckpointPath` (2026-07-12, 2026-08-23).
   - `KafkaTableITCase.testExactlyOnceSink`: "Failed to wait job finish" 
(2026-08-23).
   
   ## What
   
   Four clean cherry-picks, in the original order:
   
   - `887d5941` [hotfix] Stabilize KafkaWriterFaultToleranceITCase 
exception-on-unavailable tests
   - `2d441987` [FLINK-39699][tests] Wait for completed checkpoint stats in 
KafkaSinkITCase
   - `443c0f32` [FLINK-39699][tests] Wait for partitions assignment in 
KafkaSinkITCase
   - `84d2ee7a` [FLINK-39723][tests] Wait for partition assignment in 
KafkaTableTestBase.createTestTopic
   
   Unlike the `v4.0` backport (#259), the partition-assignment commit is 
included: `v5.0` already has 
`KafkaUtil.createNewTopicAndWaitForPartitionAssignment` via FLINK-39234.
   
   ## Verification
   
   - `mvn -pl flink-connector-kafka 
-Dtest='KafkaWriterFaultToleranceITCase,KafkaSinkITCase,KafkaTableITCase' test` 
on `v5.0` with Flink 2.1.0: 117 tests, 0 failures.
   - `spotless:check` passes.
   
   ## Brief change log
   
   - Test-only changes, no production code touched.
   
   ## Does this pull request potentially affect one of the following parts:
   
   - Dependencies (does it add or upgrade a dependency): no
   - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: no
   - The serializers: no
   - The runtime per-record code paths (performance sensitive): no
   - Anything that affects deployment or recovery: no
   - The S3 file system connector: no
   
   ## Documentation
   
   - Does this pull request introduce a new feature? no
   - If yes, how is the feature documented? not applicable
   
   ## AI disclosure
   
   - [x] This pull request was created with the help of an AI tool (Claude 
Code). The cherry-picks were selected and verified locally by the author.
   


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