feat: Add the CONTINUOUS Job type to `.google.cloud.bigquery.reservation.v1.Assignment.JobType` for continuous SQL jobs
feat: Add a new field `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
docs: Update the `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 are `OUTPUT_ONLY`
docs: Remove the section about `EDITION_UNSPECIFIED` in the comment for `slot_capacity` in `.google.cloud.bigquery.reservation.v1.Reservation` to clarify that
PiperOrigin-RevId: 731341086
feat: Add a new field `is_flat_rate` to `.google.cloud.bigquery.reservation.v1.CapacityCommitment` to distinguish between flat rate and edition commitments
docs: Clarify that `Autoscale.current_slots` in message `.google.cloud.bigquery.reservation.v1.Reservation` can temporarily be larger than `Autoscale.max_slots` if users reduce `Autoscale.max_slots`
docs: Update comment for `slot_capacity` in message `.google.cloud.bigquery.reservation.v1.Reservation` to provide more clarity about reservation baselines, committed slots and autoscaler SKU charges when the baseline exceeds committed slots
docs: Update comments for `commitment_start_time` and `commitment_end_time` in message `.google.cloud.bigquery.reservation.v1.CapacityCommitment` to provide details on how these values are affected by commitment renewal
PiperOrigin-RevId: 702079972
chore: disallow "transport=rest" for services where numeric enums are not confirmed to be supported (except in PHP and Java)
PiperOrigin-RevId: 493113566
feat: Reservation objects now contain a creation time and an update time
feat: Added commitment_start_time to capacity commitments
feat: Force deleting capacity commitments is allowed while reservations with active assignments exist
feat: ML_EXTERNAL job type is supported
feat: Optional id can be passed into CreateCapacityCommitment and CreateAssignment
docs: Clarified docs for None assignments
fix!: Fixed pattern for BiReservation object
BREAKING_CHANGE: Changed from `bireservation` to `biReservation`
PiperOrigin-RevId: 394129271
In particular this applies to Java and Python microgenerators.
With this change `java_gapic_*` and `py_gapic_*` rules mean microgenerator versions. The monolith versions of the rules are named as `java_gapic_*_legacy` and `py_gapic_*_legacy` respectively.
Also change Ads BAZEL template to reflect the change in default rule names.
Also change `DO NOT OVERRIDE` comment warnings meaning (to reflect that now by default microgenerator rules are generated and the generated version must be accepted only if the API is being migrated to the microgenerator).
PiperOrigin-RevId: 346227314
BREAKING CHANGE: update package names to avoid conflict with google-cloud-bigquery
The google-cloud-bigquery package uses the `google.cloud.bigquery` path as a
plain Python module, not a namespace package. When this package and
google-cloud-bigquery are installed in the same environment, conflicts can
result.
PiperOrigin-RevId: 339531446
BREAKING CHANGE: update package names to avoid conflict with google-cloud-bigquery
The google-cloud-bigquery package uses the `google.cloud.bigquery` path as a
plain Python module, not a namespace package. When this package and
google-cloud-bigquery are installed in the same environment, conflicts can
result.
PiperOrigin-RevId: 339048690
