[
https://issues.apache.org/jira/browse/FLINK-18307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17148773#comment-17148773
]
Arvid Heise edited comment on FLINK-18307 at 6/30/20, 3:29 PM:
---------------------------------------------------------------
Since https://issues.apache.org/jira/browse/FLINK-18433 could be traced back to
this change, I was wondering if we should add a warning for the next 1-3 major
releases when a slaves file is present but a workers is not?
It would especially help for users in the future that upgrade from 9 -> 12 (or
so), so that they might not study release notes fully and it's a much more
subtle error than any change to public evolving interfaces.
was (Author: aheise):
Since https://issues.apache.org/jira/browse/FLINK-18433 could be traced back to
this change, I was wondering if we should add a warning for the next 1-3 major
releases when a slaves file is present but a workers is not?
> Replace "slave" file name with "workers"
> ----------------------------------------
>
> Key: FLINK-18307
> URL: https://issues.apache.org/jira/browse/FLINK-18307
> Project: Flink
> Issue Type: Sub-task
> Components: Deployment / Scripts
> Reporter: Stephan Ewen
> Assignee: Stephan Ewen
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.11.0
>
>
> See parent issue for a discussion of the rationale.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
