[
https://issues.apache.org/jira/browse/BEAM-4028?focusedWorklogId=661730&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-661730
]
ASF GitHub Bot logged work on BEAM-4028:
----------------------------------------
Author: ASF GitHub Bot
Created on: 07/Oct/21 16:01
Start Date: 07/Oct/21 16:01
Worklog Time Spent: 10m
Work Description: TheNeuralBit commented on a change in pull request
#15652:
URL: https://github.com/apache/beam/pull/15652#discussion_r724322999
##########
File path: sdks/python/apache_beam/runners/common.py
##########
@@ -98,41 +98,6 @@ def logging_name(self):
return self.step_name
-# TODO(BEAM-4028): Move DataflowNameContext to Dataflow internal code.
Review comment:
Ok internal changes are done, and I bumped the beam-master container.
Testing now.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 661730)
Time Spent: 7h 20m (was: 7h 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: P2
> Fix For: Not applicable
>
> Time Spent: 7h 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
(v8.3.4#803005)
