[
https://issues.apache.org/jira/browse/FLINK-30343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17653817#comment-17653817
]
Matthias Pohl commented on FLINK-30343:
---------------------------------------
I'm not sure whether it's worth it to start on FLINK-30338 while FLINK-26522.
If FLINK-26522 is resolved in the way it is described in its comment section
right now, the {{MultipleComponent*}} classes would either go away or become
what's {{DefaultLeaderElectionService}} right now with slight adaptations.
Therefore, it would make sense to rather migrate the test cases that are
implemented for the {{MultiComponent*}} as part of FLINK-26522 than migrating
the legacy test cases to what's now under the {{MultipleComponent*}} leader
election as part of FLINK-30338 just to migrate them back as part of
FLINK-26522 again. It seems to be extra effort without any additional value.
WDYT?
> Migrate KubernetesLeaderElectionAndRetrievalITCase
> --------------------------------------------------
>
> Key: FLINK-30343
> URL: https://issues.apache.org/jira/browse/FLINK-30343
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Affects Versions: 1.16.0, 1.17.0
> Reporter: Matthias Pohl
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
