apache/beam

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

Open

#38.310 aberto em 28 de abr. de 2026

Ver no GitHub
 (3 comments) (0 reactions) (1 assignee)Java (7.313 stars) (4.097 forks)batch import
P2good first issueionew feature

Description

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

Guia do colaborador

Pilha de tecnologia
java
Domain
data
Tipo Issue
feature
DifficultyDificuldade de implementação estimada para um novo contribuidor, de 1 para alterações muito pequenas a 5 para trabalho de nível especializado.
4
Tempo estimadoUm intervalo de tempo aproximado para um colaborador experiente investigar, implementar, testar e preparar um pull request.
1-2 days
Status da atividadeQuão disponível o issue aparece agora: novo, ativo, obsoleto, bloqueado ou aguardando entrada do mantenedor.
active
ClarityCom que clareza o issue explica a mudança esperada, os critérios de aceitação e a próxima etapa.
mostly clear
Prerequisites
Java programmingApache Beam basicsBigQuery API
Simpatia para novatosUma pontuação de 1 a 100 que estima o quão acessível este issue é para colaboradores iniciantes.
25
Direção de pesquisa
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.