[
https://issues.apache.org/jira/browse/FLINK-40618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martijn Visser resolved FLINK-40618.
------------------------------------
Fix Version/s: kafka-5.1.0
Resolution: Fixed
Fixed in apache/flink-connector-kafka:main
beb52b437bb1b049dce7049724084ed21e73926a
> Connectors/Kafka: Run SourceTopicIntegrity test in the integration-test phase
> -----------------------------------------------------------------------------
>
> Key: FLINK-40618
> URL: https://issues.apache.org/jira/browse/FLINK-40618
> Project: Flink
> Issue Type: Bug
> Reporter: Purushottam Sinha
> Assignee: Purushottam Sinha
> Priority: Major
> Labels: pull-request-available
> Fix For: kafka-5.1.0
>
>
> SourceTopicIntegrityTest is a heavyweight integration test -- it starts a
> Testcontainers Kafka broker and a 3-TaskManager MiniCluster and drives
> savepoint/restore -- but its *Test suffix places it in the unit-test surefire
> execution (forkCount=4, 1GB heap). Its heavyweight siblings in the same
> package, KafkaSourceITCase and KafkaSourceMigrationITCase, are already named
> *ITCase and run in the integration-test execution (forkCount=2, 2GB heap,
> reuseForks=false).
> h3. Proposed change
> Rename SourceTopicIntegrityTest -> SourceTopicIntegrityITCase so it is picked
> up by the integration-test phase, consistent with those siblings. This
> reduces the number of concurrent Testcontainers-Kafka + MiniCluster forks and
> gives the test more heap and a fresh JVM per class. This is a
> test-classification cleanup justified by the precedence of KafkaSourceITCase
> / KafkaSourceMigrationITCase.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
