You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Feature Request]: Add possibility of configuring per-job reservation slots in BigQueryIO connector #41287
BigQuery load jobs can use either the shared slot pool or reserved slots. Currently, when using BigQueryIO, using reserved slots relies on a reservation assignment being configured for the project.
This makes it difficult to control reservation usage for individual Beam workloads. Assigning a PIPELINE reservation at the project level affects other applicable jobs in the same project, which might not be desirable when only specific Beam workloads should consume a particular reservation.
The BigQuery API supports specifying a reservation directly at the job level through JobConfiguration.reservation. The field accepts a reservation in the following format: projects/{project}/locations/{location}/reservations/{reservation}. If it is not specified, BigQuery falls back to its reservation-assignment rules.
Proposed change
Add an optional withReservation(...) configuration to BigQueryIO, for example:
When configured, BigQueryIO should propagate this value to JobConfiguration.reservation for the BigQuery jobs it creates. When it is not configured, the existing behavior should remain unchanged.
This would allow Beam users to route specific BigQuery jobs to a reservation without requiring a project-wide reservation assignment.
Issue Priority
Priority: 2 (default / most feature requests should be filed as P2)
Activity
mgorsk1 commentedon Nov 13, 2026
.take-issue