@tillrohrmann Currently, `YARNHighAvailabilityITCase` is only a test for legacy mode. If we want to maintain `YARNHighAvailabilityITCase` until a total removal of legacy mode, then the precondition of this PR runs into false. That is, `YARNHighAvailabilityITCase` isn't inactive test. If so, please close this and wait for the removal happens.
However, what is a regression of that would happen? If we say any touch of the legacy code is aimed at the removal, then it is no need to maintain a test for that. It looks like we would maintain the legacy mode for quite a long time(at lease for the next several version). If so, I would prevent myself from any idea of "cleanup" them. [ Full content available at: https://github.com/apache/flink/pull/6716 ] This message was relayed via gitbox.apache.org for [email protected]
