[
https://issues.apache.org/jira/browse/BEAM-9667?focusedWorklogId=415020&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-415020
]
ASF GitHub Bot logged work on BEAM-9667:
----------------------------------------
Author: ASF GitHub Bot
Created on: 02/Apr/20 20:10
Start Date: 02/Apr/20 20:10
Worklog Time Spent: 10m
Work Description: lostluck commented on pull request #11287: [BEAM-9667]
Allow metrics in DoFn Setup
URL: https://github.com/apache/beam/pull/11287
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 415020)
Time Spent: 0.5h (was: 20m)
> Allow metrics use during DoFn Setup
> -----------------------------------
>
> Key: BEAM-9667
> URL: https://issues.apache.org/jira/browse/BEAM-9667
> Project: Beam
> Issue Type: Bug
> Components: sdk-go
> Reporter: Robert Burke
> Priority: Minor
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> User found a bug where runners were crashing because the PTransform label for
> metrics were not being populated by the Go SDK. It was narrowed down to the
> Setup method not populating the PTransformId context, but providing a bundle
> context.
> As long as users aren't caching the context in their DoFns, populating the
> PTransformID for Setup should be safe as long as we don't cache it, as the
> bundle Id will be different for subsequent executions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
