apache/beam

BigQueryBatchFileLoads dynamic destination

Open

#20,242 opened on Jun 4, 2022

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

Repository metrics

Stars
 (7,313 stars)
PR merge metrics
 (Avg merge 6d) (243 merged PRs in 30d)

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

Research direction
Investigate how temporary tables are handled in BigQueryBatchFileLoads when using dynamic destinations. Ensure the triggering frequency properly merges the temporary tables into the final destination.
Tech stack
java
Domain
backend
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-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
JavaApache BeamBigQuery
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60