[ 
https://issues.apache.org/jira/browse/FLINK-25030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17448437#comment-17448437
 ] 

Matthias commented on FLINK-25030:
----------------------------------

FLINK-24261 and FLINK-25030 are related in a way that the same test is failing. 
But the failure reason is different. I linked them, anyway.

> Unexpected record in KafkaSourceITCase$IntegrationTests.testMultipleSplits
> --------------------------------------------------------------------------
>
>                 Key: FLINK-25030
>                 URL: https://issues.apache.org/jira/browse/FLINK-25030
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / Kafka
>    Affects Versions: 1.14.1
>            Reporter: Matthias
>            Priority: Major
>              Labels: test-stability
>         Attachments: logs-ci_build-test_ci_build_kafka_gelly-1637699602.zip
>
>
> We experienced a test failure in 
> {{KafkaSourceITCase$IntegrationTests.testMultipleSplits}} in our Flink fork 
> for 1.14 due to an unexpected record:
> {code}
> [...]
> Nov 23 21:10:19 [ERROR] 
> org.apache.flink.connector.kafka.source.KafkaSourceITCase$IntegrationTests.testMultipleSplits{TestEnvironment,
>  ExternalContext}[1]
> Nov 23 21:10:19 [ERROR]   Run 1: 
> KafkaSourceITCase$IntegrationTests>SourceTestSuiteBase.testMultipleSplits:160 
> Nov 23 21:10:19 Expected: Records consumed by Flink should be identical to 
> test data and preserve the order in multiple splits
> Nov 23 21:10:19      but: Unexpected record 
> '2-13N3fae7bfL1iEMF3I0TaWGC57vrflv' at position 367
> Nov 23 21:10:19 Current progress of multiple split test data validation:
> Nov 23 21:10:19 Split 0 (115/115): 
> Nov 23 21:10:19 0-C7bHGoulUrqjQqGM8PiVI6BS9B3Okq2PJdf3EBas3G
> Nov 23 21:10:19 0-GRt5T5YYDsgq1t0UBt3cUjvnktIbz
> [...]
> {code}
> I verified that we do not touch kafka-related in the Fork (by going through 
> the patches with {{grep -i 'kafka\|source'}}). I added the pipeline build 
> artifacts to this ticket.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to