[
https://issues.apache.org/jira/browse/BEAM-9997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17135241#comment-17135241
]
Beam JIRA Bot commented on BEAM-9997:
-------------------------------------
This issue is assigned but has not received an update in 30 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> 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
> Assignee: Kyle Weaver
> Priority: P2
> Labels: portability-spark, stale-assigned
>
> 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)
