Github user zentol commented on the issue:
https://github.com/apache/flink/pull/2146
That is a known and intended behavior. It is the users responsibility to
make sure that no naming conflicts arise, either by providing unique
job/task/operator names or modifying the scope formats.
Regarding your suggestion, even if we exclude the disparity between the
name a user expects and the name we might provide, there is still the issue
that it (sadly) doesn't actually solve anything.
Assume 2 TaskManagers, both exporting a metric `MyJob.metric` and
`MyJob1.metric`.
You cannot guarantee that both versions of `MyJob.metric` actually belong
to the same job.
You can't even make the guarantee that all values a TM exposes as
`MyJob.metric` belong to a single job.
This problem also exists right; the only difference is that you only have 1
set of inconsistent data, and not 2.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
