flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-5977) Rename MAX_ATTEMPTS_HISTORY_SIZE key
Date Wed, 22 Mar 2017 15:38:41 GMT

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

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

Github user StephanEwen commented on the issue:

    https://github.com/apache/flink/pull/3592
  
    Thanks for the pull request.
    This has actually already been fixed in https://github.com/apache/flink/commit/81a143f6b42cf39d56a36222d14b5db0cc54addb
    
    The commit also retains the old key as a deprecated parameter for backwards compatibility.


> Rename MAX_ATTEMPTS_HISTORY_SIZE key
> ------------------------------------
>
>                 Key: FLINK-5977
>                 URL: https://issues.apache.org/jira/browse/FLINK-5977
>             Project: Flink
>          Issue Type: Bug
>          Components: JobManager
>    Affects Versions: 1.3.0
>            Reporter: Chesnay Schepler
>            Priority: Blocker
>             Fix For: 1.3.0
>
>
> The JobManagerOptions#MAX_ATTEMPTS_HISTORY_SIZE key is inconsistent with other jobmanager
related keys in that it starts with "job-manager" instead of "jobmanager".



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message