[
https://issues.apache.org/jira/browse/FLINK-40048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martijn Visser resolved FLINK-40048.
------------------------------------
Fix Version/s: 2.4.0
Resolution: Fixed
Fixed in apache/flink:master 4859b981e31cc49f38af66adb392545c411dd096
> Refactor and re-enable flink-sql-client-test E2E test
> -----------------------------------------------------
>
> Key: FLINK-40048
> URL: https://issues.apache.org/jira/browse/FLINK-40048
> Project: Flink
> Issue Type: Technical Debt
> Components: Table SQL / Client, Tests
> Reporter: Martijn Visser
> Assignee: Martijn Visser
> Priority: Major
> Fix For: 2.4.0
>
>
> Triggered by https://github.com/apache/flink/pull/27924 I looked into the
> flink-sql-client-test. This module
> (flink-end-to-end-tests/flink-sql-client-test/) carries dead-weight Kafka
> dependencies:
> 1. flink-sql-connector-kafka:3.0.0-1.17 -> pinned to a Flink 1.17-era version
> of an externalized connector (removed from main repo in FLINK-30859)
> 2. kafka-clients:3.9.2 (test scope) -> only used by sendMessages(), which is
> only called from testMatchRecognize()
> 3. testcontainers-kafka (test scope) -> Kafka container only started for the
> disabled test
> testMatchRecognize() has been @Disabled("Disable due to Kafka connector need
> to release a new version 2.0.") since the connector was externalized and has
> never been re-enabled. It is also the only E2E test for MATCH_RECOGNIZE in
> the entire repo.
> I'd recommend to remove Kafka and re-enable this test using the filesystem
> source instead
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
