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

Till Rohrmann commented on FLINK-10436:
---------------------------------------

The {{.withDeprecatedKeys}} has the nice property that it falls back to 
{{JobManagerOptions.ADDRESS.key()}} if {{rest.address}} has not been specified. 
If we remove this, then we require our users to always change both 
configuration parameters.

Maybe we need to introduce a {{ConfigOption#withFallback}} which defines such a 
relationship without printing the deprecation warning.

> Example config uses deprecated key jobmanager.rpc.address
> ---------------------------------------------------------
>
>                 Key: FLINK-10436
>                 URL: https://issues.apache.org/jira/browse/FLINK-10436
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Startup Shell Scripts
>    Affects Versions: 1.7.0
>            Reporter: Ufuk Celebi
>            Assignee: TisonKun
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.7.0
>
>
> The example {{flink-conf.yaml}} shipped as part of the Flink distribution 
> (https://github.com/apache/flink/blob/master/flink-dist/src/main/resources/flink-conf.yaml)
>  has the following entry:
> {code}
> jobmanager.rpc.address: localhost
> {code}
> When using this key, the following deprecation warning is logged.
> {code}
> 2018-09-26 12:01:46,608 WARN  org.apache.flink.configuration.Configuration    
>               - Config uses deprecated configuration key 
> 'jobmanager.rpc.address' instead of proper key 'rest.address'
> {code}
> The example config should not use deprecated config options.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to