apache/beam

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

Open

#34,076 opened on 2025年2月26日

GitHub で見る
 (9 comments) (0 reactions) (2 assignees)Java (7,313 stars) (4,097 forks)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
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
4
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-2 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
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.