You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Pablo Estrada (JIRA)" <ji...@apache.org> on 2019/04/30 17:38:00 UTC
[jira] [Resolved] (BEAM-4028) Step / Operation naming should rely
on a NameContext class
[ https://issues.apache.org/jira/browse/BEAM-4028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pablo Estrada resolved BEAM-4028.
---------------------------------
Resolution: Fixed
Fix Version/s: Not applicable
> 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
> Labels: triaged
> Fix For: Not applicable
>
> Time Spent: 5h 40m
> 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)