Release Google.Cloud.BigQuery.Reservation.V1 version 2.7.0 #14373
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes in this release:
New features
replication_status
to.google.cloud.bigquery.reservation.v1.Reservation
to provide visibility into errors that could arise during Disaster Recovery(DR) replication (commit fecbe42).google.cloud.bigquery.reservation.v1.Assignment.JobType
for continuous SQL jobs (commit fecbe42)enable_gemini_in_bigquery
to.google.cloud.bigquery.reservation.v1.Assignment
that indicates if "Gemini in Bigquery"(https://cloud.google.com/gemini/docs/bigquery/overview) features are enabled for the reservation assignment (commit fecbe42)Documentation improvements
google.api.field_behavior
for the.google.cloud.bigquery.reservation.v1.Reservation.primary_location
and.google.cloud.bigquery.reservation.v1.Reservation.original_primary_location
fields to clarify that they areOUTPUT_ONLY
(commit fecbe42)EDITION_UNSPECIFIED
in the comment forslot_capacity
in.google.cloud.bigquery.reservation.v1.Reservation
to clarify that (commit fecbe42)