[
https://issues.apache.org/jira/browse/BEAM-4028?focusedWorklogId=91447&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-91447
]
ASF GitHub Bot logged work on BEAM-4028:
----------------------------------------
Author: ASF GitHub Bot
Created on: 16/Apr/18 19:41
Start Date: 16/Apr/18 19:41
Worklog Time Spent: 10m
Work Description: pabloem opened a new pull request #5135: [BEAM-4028]
Transitioning MapTask objects to NameContext
URL: https://github.com/apache/beam/pull/5135
Transitioning the `operation_specs.MapTask` to rely fully on `NameContext`
for step naming.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 91447)
Time Spent: 3h 20m (was: 3h 10m)
> 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 20m
> 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)
