apache/beam

[Bug][Go]: Metrics incremented in Setup methods are not recalled.

Open

#27,038 创建于 2023年6月6日

在 GitHub 查看
 (2 评论) (0 反应) (0 负责人)Java (7,313 star) (4,097 fork)batch import
P3buggogood first issue

描述

What happened?

Because the ParDo Setup context is uncached metrics initialized in Setup are lost, which is unexpected. Work done in setup, while logically outside of a bundle, will be under the context of the first bundle to execute that transform.

So there needs to be a way to transfer/extract the metrics from the Setup context so they are recorded back to the runner.

Issue Priority

Priority: 3 (minor)

Issue Components

  • Component: Python SDK
  • Component: Java SDK
  • Component: Go SDK
  • Component: Typescript SDK
  • Component: IO connector
  • Component: Beam examples
  • Component: Beam playground
  • Component: Beam katas
  • Component: Website
  • Component: Spark Runner
  • Component: Flink Runner
  • Component: Samza Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner

贡献者指南

技术栈
go
领域
data
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Go programmingApache Beam basicsmetrics concepts
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
25
研究方向
Investigate the uncached Setup context in pardo.go (line 104). Understand how metrics are currently lost and propose a mechanism to extract/transfer them from the Setup context to be recorded back to the runner. Consider caching the Setup context or piping metrics differently.
[Bug][Go]: Metrics incremented in Setup methods are not recalled. · apache/beam#27038 | Good First Issue