[
https://issues.apache.org/jira/browse/FLINK-14271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16940284#comment-16940284
]
Zhu Zhu commented on FLINK-14271:
---------------------------------
{{The RestartPipelinedRegionStrategy}} was never production ready and it is not
a public interface(the failover config "region" now points to
{{AdaptedRestartPipelinedRegionStrategyNG}}).
So I think it's safe to remove it.
[~trohrmann] is it valid to remove it directly? or we can only deprecate it in
1.10 and remove it in a future release?
> Deprecate legacy RestartPipelinedRegionStrategy
> -----------------------------------------------
>
> Key: FLINK-14271
> URL: https://issues.apache.org/jira/browse/FLINK-14271
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.10.0
> Reporter: Zhu Zhu
> Priority: Major
> Fix For: 1.10.0
>
>
> The legacy {{RestartPipelinedRegionStrategy}} has been superseded by
> {{AdaptedRestartPipelinedRegionStrategyNG}} in Flink 1.9.
> It heavily depends on ExecutionGraph components and becomes a blocker for a
> clean scheduler re-architecture.
> We should deprecate it for further removal.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)