[ 
https://issues.apache.org/jira/browse/FLINK-32582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-32582:
-----------------------------------
    Labels: pull-request-available stale-major  (was: pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issues has been marked as 
Major but is unassigned and neither itself nor its Sub-Tasks have been updated 
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this 
ticket is a Major, please either assign yourself or give an update. Afterwards, 
please remove the label or in 7 days the issue will be deprioritized.


> Move TypeSerializerUpgradeTestBase from Kafka connector into 
> flink-connector-common
> -----------------------------------------------------------------------------------
>
>                 Key: FLINK-32582
>                 URL: https://issues.apache.org/jira/browse/FLINK-32582
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / Common
>            Reporter: Matthias Pohl
>            Priority: Major
>              Labels: pull-request-available, stale-major
>
> The externalization of connectors made caused problems with the Flink's test 
> data generation. The Kafka connector relied on TypeSerializerUpgradeTestBase 
> for some test cases which was fine prior to FLINK-27518 where the test data 
> generation was handled individually.
> With FLINK-27518 the process was automated in Flink 1.18. For now, the 
> TypeSerializerUpgradeTestBase class was just copied over into the Kafka 
> connector since it was the only connector that would utilize this test base.
> But we might want to provide a more generalized solution where the test base 
> is provided by {{flink-connector-common}} to offer a generalized approach for 
> any connector.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to