[ 
https://issues.apache.org/jira/browse/FLINK-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15555090#comment-15555090
 ] 

ASF GitHub Bot commented on FLINK-4768:
---------------------------------------

GitHub user StephanEwen opened a pull request:

    https://github.com/apache/flink/pull/2607

    [FLINK-4768] [core] Migrate high-availability configuration parameters to 
ConfigOptions

    This is based on #2605 - so only the later commit is relevant.
    
    This basically moves all High Availability related options from the 
`ConfigConstants` to `HighAvailabilityOptions`.
    
    It nicely shows how maintaining keys, deprecated keys, and default values 
together in an option is much easier.

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

    $ git pull https://github.com/StephanEwen/incubator-flink ha_config_options

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

    https://github.com/apache/flink/pull/2607.patch

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

    This closes #2607
    
----
commit ee9f80c05a473394564010f5e2004d527cdc3891
Author: Stephan Ewen <[email protected]>
Date:   2016-10-07T13:24:44Z

    [FLINK-4764] [core] Introduce Config Options
    
    This is a more concise and maintainable way to define configuration keys, 
default values,
    deprecated keys, etc.

commit 1a843465f32ce6dd1e7215773c80b62364b699c9
Author: Stephan Ewen <[email protected]>
Date:   2016-10-07T13:25:18Z

    [FLINK-4768] [core] Migrate high-availability configuration parameters to 
ConfigOptions

----


> Migrate High Availability configuration options
> -----------------------------------------------
>
>                 Key: FLINK-4768
>                 URL: https://issues.apache.org/jira/browse/FLINK-4768
>             Project: Flink
>          Issue Type: Sub-task
>            Reporter: Stephan Ewen
>




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

Reply via email to