apache / apache/beam

Improve step names in portable runners

Open
#20,183 0 comments 0 reactions 0 assignees View on GitHub
improvement P3 portability runners spark
Dominant language
Java
Stars
8.7k
Forks
4.7k
Avg merge
1d 20h
Merged PRs (30d)
196

Description

Step names are currently inconsistent between runners. This is probably unavoidable due to fusion, but we should design a system that is more consistent between runners so that most metric queries against the Fn API runner can also be used with the portable Flink and Spark runners.

Spark Runner:
MetricKey(step=ref_AppliedPTransform_count1_17, metric=MetricName(namespace=ns, name=counter), labels={}): 2
MetricKey(step=ref_AppliedPTransform_count2_18, metric=MetricName(namespace=ns, name=counter), labels={}): 4
...

Fn API Runner:
MetricKey(step=count1, metric=MetricName(namespace=ns, name=counter), labels={}): 2,
MetricKey(step=count2, metric=MetricName(namespace=ns, name=counter), labels={}): 4

Imported from Jira [BEAM-9997](https://issues.apache.org/jira/browse/BEAM-9997). Original Jira may contain additional context.
Reported by: ibzib.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.