[jira] [Work logged] (BEAM-4028) Step / Operation naming should rely on a NameContext class

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

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

                Author: ASF GitHub Bot
            Created on: 06/Apr/18 18:27
            Start Date: 06/Apr/18 18:27
    Worklog Time Spent: 10m 
      Work Description: pabloem opened a new pull request #5043: [BEAM-4028] Adding NameContext to Python SDK.
URL: https://github.com/apache/beam/pull/5043
 
 
   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.
   
   This change starts by creating name context classes and passing them into operations. Next steps are:
   
   - Migrating operations away from using their operation names, and removing them from the object definition in `operations.pxd`, and clean all the operation creating logic.
   
   

----------------------------------------------------------------
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:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 88549)
            Time Spent: 10m
    Remaining Estimate: 0h

> 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: 10m
>  Remaining Estimate: 0h
>
> Steps can have different steps 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)