apache/beam

[Feature Request]: Creation of BigQuery clone table via BigQueryIO

Open

#38,310 opened on 2026年4月28日

GitHub で見る
 (3 comments) (0 reactions) (1 assignee)Java (7,313 stars) (4,097 forks)batch import
P2good first issueionew feature

説明

What would you like to happen?

BigQuery IO does not have direct support for dedicated clone operations. https://beam.apache.org/documentation/io/built-in/google-bigquery/

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

コントリビューターガイド

技術スタック
java
領域
data
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
4
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-2 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
active
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
mostly clear
前提条件
Java programmingApache Beam basicsBigQuery API
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
25
調査方針
Examine the existing BigQueryIO implementation in the Java SDK (specifically the write and read transforms). Understand the BigQuery clone table API from Google Cloud documentation. Look at the comments and any linked discussions in issue #38310 for design input. Propose a new transform following the pattern of existing IO operations, considering table cloning semantics and error handling.