[
https://issues.apache.org/jira/browse/FLINK-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14635819#comment-14635819
]
ASF GitHub Bot commented on FLINK-2205:
---------------------------------------
Github user fhueske commented on the pull request:
https://github.com/apache/flink/pull/927#issuecomment-123477253
Hi @ebautistabar, thanks for the pull request!
I would also like to change the key "Number of execution retries" to "Max.
number of execution retries" (or similiar) to make sure, that users understand
that this is the configured max number of retries and not the number of times a
task execution was actually retried.
> Confusing entries in JM Webfrontend Job Configuration section
> -------------------------------------------------------------
>
> Key: FLINK-2205
> URL: https://issues.apache.org/jira/browse/FLINK-2205
> Project: Flink
> Issue Type: Bug
> Components: Webfrontend
> Affects Versions: 0.9
> Reporter: Fabian Hueske
> Priority: Minor
> Labels: starter
>
> The Job Configuration section of the job history / analyze page of the
> JobManager webinterface contains two confusing entries:
> - {{Number of execution retries}} is actually the maximum number of retries
> and should be renamed accordingly. The default value is -1 and should be
> changed to "deactivated" (or 0).
> - {{Job parallelism}} which is -1 by default. A parallelism of -1 is not very
> meaningful. It would be better to show something like "auto"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
