apache/beam

BigQueryBatchFileLoads dynamic destination

Open

#20,242 opened on Jun 4, 2022

View on GitHub
 (6 comments) (0 reactions) (1 assignee)Java (7,313 stars) (4,097 forks)batch import
P3bugdocumentationgcpgood first issueiopython

Description

I am trying to use BigQueryBatchFileLoads to upload data from pubsub. It works fine for a single table, but when I try to use a dynamic destination such as destination=lambda elem: "my_project:my_dataset." **** elem["sensor_key"], it just makes a new table for each time the triggering_frequency procs. I know it makes temporary tables before loading it all into one, but it never loads them. It just creates more and more tables.

Imported from Jira BEAM-9917. Original Jira may contain additional context. Reported by: tordaut.

Contributor guide

Tech stack
java
Domain
databackend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
JavaApache BeamBigQuery connectorDynamic destinations
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
Investigate the BigQueryBatchFileLoads transform implementation, focusing on the dynamic destination handling. Look at the source code in the Beam repository (likely in sdks/java/io/bigquery). Check if the temporary table creation and final load logic correctly handle dynamic destinations. Review the Jira issue BEAM 9917 for additional context. Ensure that the triggering frequency and destination lambda interaction is correct.