apache/beam

[Feature Request]: Cache the BigQuery table definition instead of calling tables.get() from every worker

Open

#34,076 建立於 2025年2月26日

在 GitHub 查看
 (9 留言) (0 反應) (2 負責人)Java (7,313 star) (4,097 fork)batch import
P2good first issuenew featurepythonstale

描述

What would you like to happen?

When calling BigQuery's tables.get method, today, we are calling it from every Dataflow worker. This is resulting in customers hitting Quota issues. Please can we cache the Table definition and re-use for all workers instead of calling the method from every worker.

https://cloud.google.com/bigquery/docs/reference/rest/v2/tables/get

https://github.com/apache/beam/blob/9a1e7bf4cd399177e5de7fe28bad741cade452a5/sdks/python/apache_beam/io/gcp/bigquery.py#L902-L903

https://github.com/apache/beam/blob/9a1e7bf4cd399177e5de7fe28bad741cade452a5/sdks/python/apache_beam/io/gcp/bigquery_tools.py#L565

Issue Priority

Priority: 2 (default / most feature requests should be filed as P2)

Issue Components

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

貢獻者指南

技術棧
pythongcp
領域
backenddatacloud
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
blocked
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
PythonBigQuery APICachingApache Beam SDK
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
35
研究方向
Investigate the existing calls to tables.get() in the Python SDK, specifically in bigquery.py (line 902-903) and bigquery tools.py (line 565) as linked in the issue. Determine a caching strategy that avoids calling the API from every worker. Consider using a shared cache across workers or a lazy initialization pattern. Review the 9 comments in the issue for any proposed solutions or maintainer feedback.
[Feature Request]: Cache the BigQuery table definition instead of calling tables.get() from every worker · apache/beam#34076 | Good First Issue