[
https://issues.apache.org/jira/browse/FLINK-4253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15432131#comment-15432131
]
ASF GitHub Bot commented on FLINK-4253:
---------------------------------------
Github user ramkrish86 commented on the issue:
https://github.com/apache/flink/pull/2342
@uce
Thank you very much for checking it out. I can see in the branch that you
have created you have updated some doc comment that I had added - from 'config'
to 'key' and some missing places. Good on you. Thanks once again. Do let me
know if you want me to help out in this if some more places you feel it is
missing.
> Rename "recovery.mode" config key to "high-availability"
> --------------------------------------------------------
>
> Key: FLINK-4253
> URL: https://issues.apache.org/jira/browse/FLINK-4253
> Project: Flink
> Issue Type: Improvement
> Reporter: Ufuk Celebi
> Assignee: ramkrishna.s.vasudevan
>
> Currently, HA is configured via the following configuration keys:
> {code}
> recovery.mode: STANDALONE // No high availability (HA)
> recovery.mode: ZOOKEEPER // HA
> {code}
> This could be more straight forward by simply renaming the key to
> {{high-availability}}. Furthermore, the term {{STANDALONE}} is overloaded. We
> already have standalone cluster mode.
> {code}
> high-availability: NONE // No HA
> high-availability: ZOOKEEPER // HA via ZooKeeper
> {code}
> The {{recovery.mode}} configuration keys would have to be deprecated before
> completely removing them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
