[
https://issues.apache.org/jira/browse/FLINK-6051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chesnay Schepler closed FLINK-6051.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.2.1
1.3.0
1.2: 9206df666057eb32f82c93f537a04466c67b9fc4
1.3: 609b2577a6490dbfa5eb48fb03fd1c0f93c6c0da
> Wrong metric scope names in documentation
> -----------------------------------------
>
> Key: FLINK-6051
> URL: https://issues.apache.org/jira/browse/FLINK-6051
> Project: Flink
> Issue Type: Bug
> Components: Documentation, Metrics
> Affects Versions: 1.2.0, 1.3.0
> Reporter: Joshua Griffith
> Priority: Minor
> Fix For: 1.3.0, 1.2.1
>
>
> FLINK-4402 fixed the following metrics names:
> metrics.scope.tm.task → metrics.scope.task
> metrics.scope.tm.operator → metrics.scope.operator
> However, the [1.2.0
> documentation|https://github.com/apache/flink/blob/dabeb74c10e755c655a06cdc8846dc7227d63cb9/docs/setup/config.md#metrics]
> lists the incorrect metric names again.
> As a side note, it would be convenient to have all of the configuration
> options documented in a machine readable format. To build docker images I
> [process the config file with
> sed|https://github.com/orgsync/docker-flink/blob/a08ec4d102b623bfba74a61d3012931e28ef92e7/Dockerfile#L36]
> to extract the options and turn them into env vars, which is how I noticed
> this issue.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
