flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From uce <...@git.apache.org>
Subject [GitHub] flink pull request: [FLINK-2893] Rename recovery configuration key...
Date Thu, 22 Oct 2015 11:05:13 GMT
GitHub user uce opened a pull request:


    [FLINK-2893] Rename recovery configuration keys

    For `ha.zookeeper` there were some static usages (not via `ConfigConstants`). After the
first commit:
    $ flink git:(0.10) grep "ha\.zookeeper" -r . | wc -l
    The file state backend configuration was always referenced via `ConfigConstants`.
    @tillrohrmann Can you have a look at this to make sure that I didn't forget anything?

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/uce/flink recovery-config

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1286
commit 607459bdbf18b505e285f43eaab35f8fe709c8dc
Author: Ufuk Celebi <uce@apache.org>
Date:   2015-10-22T10:58:26Z

    [FLINK-2893] [runtime] Rename config key prefix from 'ha.zookeeper' to 'recovery.zookeeper'

commit ed6c72706abb3312c0f7cb525a3b43b73c21ca7b
Author: Ufuk Celebi <uce@apache.org>
Date:   2015-10-22T11:00:33Z

    [FLINK-2893] [runtime] Rename config key from 'state.backend.fs.dir.recovery' => 'state.backend.fs.recoverydir'


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message