[
https://issues.apache.org/jira/browse/BEAM-11425?focusedWorklogId=522207&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-522207
]
ASF GitHub Bot logged work on BEAM-11425:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 09/Dec/20 11:58
Start Date: 09/Dec/20 11:58
Worklog Time Spent: 10m
Work Description: kamilwu commented on a change in pull request #13505:
URL: https://github.com/apache/beam/pull/13505#discussion_r539246687
##########
File path: sdks/go/pkg/beam/runners/dataflow/dataflowlib/execute.go
##########
@@ -122,3 +135,21 @@ func PrintJob(ctx context.Context, job *df.Job) {
}
log.Info(ctx, string(str))
}
+
+type dataflowPipelineResult struct {
+ JobID string
Review comment:
I had to add the `JobID()` to the `PipelineResult` interface also. But I
think it's fine, since most runners have some kind of a job ID.
----------------------------------------------------------------
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: 522207)
Time Spent: 1h 10m (was: 1h)
> [Go SDK] Support metrics querying (Dataflow)
> --------------------------------------------
>
> Key: BEAM-11425
> URL: https://issues.apache.org/jira/browse/BEAM-11425
> Project: Beam
> Issue Type: Sub-task
> Components: sdk-go
> Reporter: Kamil Wasilewski
> Assignee: Kamil Wasilewski
> Priority: P2
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> The idea of querying metrics described in the parent ticket doesn't apply to
> Dataflow runner. Instead, we can get metrics from Monitoring API (this is how
> it works in Python SDK:
> https://github.com/apache/beam/blob/master/sdks/python/apache_beam/runners/dataflow/dataflow_metrics.py)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
