[
https://issues.apache.org/jira/browse/BEAM-9997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17182455#comment-17182455
]
Beam JIRA Bot commented on BEAM-9997:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> Improve step names in portable runners
> --------------------------------------
>
> Key: BEAM-9997
> URL: https://issues.apache.org/jira/browse/BEAM-9997
> Project: Beam
> Issue Type: Improvement
> Components: runner-spark
> Reporter: Kyle Weaver
> Priority: P2
> Labels: portability-spark, stale-P2
>
> 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
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
