[
https://issues.apache.org/jira/browse/BEAM-4028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16437590#comment-16437590
]
Pablo Estrada commented on BEAM-4028:
-------------------------------------
Before closing this, this log statement should be removed
[https://github.com/apache/beam/pull/5043#discussion-diff-181442300R123]
> Step / Operation naming should rely on a NameContext class
> ----------------------------------------------------------
>
> Key: BEAM-4028
> URL: https://issues.apache.org/jira/browse/BEAM-4028
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-core
> Reporter: Pablo Estrada
> Assignee: Pablo Estrada
> Priority: Major
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> Steps can have different names depending on the runner (stage, step, user,
> system name...).
> Depending on the needs of different components (operations, logging, metrics,
> statesampling) these step names are passed around without a specific order.
> Instead, SDK should rely on `NameContext` objects that carry all the naming
> information for a single step.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
