[ 
https://issues.apache.org/jira/browse/BEAM-4028?focusedWorklogId=89451&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-89451
 ]

ASF GitHub Bot logged work on BEAM-4028:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 10/Apr/18 15:34
            Start Date: 10/Apr/18 15:34
    Worklog Time Spent: 10m 
      Work Description: pabloem commented on issue #5043: [BEAM-4028] Adding 
NameContext to Python SDK.
URL: https://github.com/apache/beam/pull/5043#issuecomment-380144985
 
 
   Run Python PostCommit
   
   

----------------------------------------------------------------
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: 89451)
    Time Spent: 1.5h  (was: 1h 20m)

> 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: 1.5h
>  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)

Reply via email to