flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fabian Hueske (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (FLINK-2893) Rename recovery configuration keys
Date Fri, 23 Oct 2015 14:10:27 GMT

     [ https://issues.apache.org/jira/browse/FLINK-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Fabian Hueske closed FLINK-2893.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 1.0

Fixed in 0.10 with 8ec828c9444711ab5956904bcffc149a5724e1e6
Fixed in 1.0 with ab2895fa988018300395557d110de23a3a2166c9

> Rename recovery configuration keys
> ----------------------------------
>
>                 Key: FLINK-2893
>                 URL: https://issues.apache.org/jira/browse/FLINK-2893
>             Project: Flink
>          Issue Type: Improvement
>    Affects Versions: 0.10
>            Reporter: Ufuk Celebi
>            Assignee: Ufuk Celebi
>             Fix For: 0.10, 1.0
>
>
> Configuration keys for recovery have different prefixes:
> {code}
> recovery.mode
> ha.zookeeper.quorum
> ha.zookeeper.etc
> {code}
> Since {{recovery.mode}} accepts {{zookeeper}} as a value, we should make the configuration
consistent by renaming the {{ha}} prefix to {{recovery}}.
> Furthermore the {{state.backend.fs.dir.recovery}} is inconsistent wrt {{ state.backend.fs.recoverydir}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message