Reference documentation and code samples for the BigQuery Reservation V1 API module Google::Cloud::Bigquery::Reservation::V1::CapacityCommitment::CommitmentPlan.
Commitment plan defines the current committed period. Capacity commitment
cannot be deleted during it's committed period.
Constants
COMMITMENT_PLAN_UNSPECIFIED
value: 0 Invalid plan value. Requests with this value will be rejected with
error code google.rpc.Code.INVALID_ARGUMENT.
FLEX
value: 3 Flex commitments have committed period of 1 minute after becoming ACTIVE.
After that, they are not in a committed period anymore and can be removed
any time.
FLEX_FLAT_RATE
value: 7 Same as FLEX, should only be used if flat-rate commitments are still
available.
TRIAL
value: 5 Trial commitments have a committed period of 182 days after becoming
ACTIVE. After that, they are converted to a new commitment based on the
renewal_plan. Default renewal_plan for Trial commitment is Flex so
that it can be deleted right after committed period ends.
MONTHLY
value: 2 Monthly commitments have a committed period of 30 days after becoming
ACTIVE. After that, they are not in a committed period anymore and can be
removed any time.
MONTHLY_FLAT_RATE
value: 8 Same as MONTHLY, should only be used if flat-rate commitments are still
available.
ANNUAL
value: 4 Annual commitments have a committed period of 365 days after becoming
ACTIVE. After that they are converted to a new commitment based on the
renewal_plan.
ANNUAL_FLAT_RATE
value: 9 Same as ANNUAL, should only be used if flat-rate commitments are still
available.
THREE_YEAR
value: 10 3-year commitments have a committed period of 1095(3 * 365) days after
becoming ACTIVE. After that they are converted to a new commitment based
on the renewal_plan.
NONE
value: 6 Should only be used for renewal_plan and is only meaningful if
edition is specified to values other than EDITION_UNSPECIFIED. Otherwise
CreateCapacityCommitmentRequest or UpdateCapacityCommitmentRequest will
be rejected with error code google.rpc.Code.INVALID_ARGUMENT. If the
renewal_plan is NONE, capacity commitment will be removed at the end of
its commitment period.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-09 UTC."],[],[],null,["# BigQuery Reservation V1 API - Module Google::Cloud::Bigquery::Reservation::V1::CapacityCommitment::CommitmentPlan (v1.6.0)\n\nVersion latestkeyboard_arrow_down\n\n- [1.6.0 (latest)](/ruby/docs/reference/google-cloud-bigquery-reservation-v1/latest/Google-Cloud-Bigquery-Reservation-V1-CapacityCommitment-CommitmentPlan)\n- [1.5.0](/ruby/docs/reference/google-cloud-bigquery-reservation-v1/1.5.0/Google-Cloud-Bigquery-Reservation-V1-CapacityCommitment-CommitmentPlan)\n- [1.4.1](/ruby/docs/reference/google-cloud-bigquery-reservation-v1/1.4.1/Google-Cloud-Bigquery-Reservation-V1-CapacityCommitment-CommitmentPlan)\n- [1.3.0](/ruby/docs/reference/google-cloud-bigquery-reservation-v1/1.3.0/Google-Cloud-Bigquery-Reservation-V1-CapacityCommitment-CommitmentPlan)\n- [1.2.0](/ruby/docs/reference/google-cloud-bigquery-reservation-v1/1.2.0/Google-Cloud-Bigquery-Reservation-V1-CapacityCommitment-CommitmentPlan)\n- [1.1.0](/ruby/docs/reference/google-cloud-bigquery-reservation-v1/1.1.0/Google-Cloud-Bigquery-Reservation-V1-CapacityCommitment-CommitmentPlan)\n- [1.0.1](/ruby/docs/reference/google-cloud-bigquery-reservation-v1/1.0.1/Google-Cloud-Bigquery-Reservation-V1-CapacityCommitment-CommitmentPlan)\n- [0.12.0](/ruby/docs/reference/google-cloud-bigquery-reservation-v1/0.12.0/Google-Cloud-Bigquery-Reservation-V1-CapacityCommitment-CommitmentPlan)\n- [0.11.2](/ruby/docs/reference/google-cloud-bigquery-reservation-v1/0.11.2/Google-Cloud-Bigquery-Reservation-V1-CapacityCommitment-CommitmentPlan)\n- [0.10.0](/ruby/docs/reference/google-cloud-bigquery-reservation-v1/0.10.0/Google-Cloud-Bigquery-Reservation-V1-CapacityCommitment-CommitmentPlan)\n- [0.9.0](/ruby/docs/reference/google-cloud-bigquery-reservation-v1/0.9.0/Google-Cloud-Bigquery-Reservation-V1-CapacityCommitment-CommitmentPlan)\n- [0.8.1](/ruby/docs/reference/google-cloud-bigquery-reservation-v1/0.8.1/Google-Cloud-Bigquery-Reservation-V1-CapacityCommitment-CommitmentPlan)\n- [0.7.0](/ruby/docs/reference/google-cloud-bigquery-reservation-v1/0.7.0/Google-Cloud-Bigquery-Reservation-V1-CapacityCommitment-CommitmentPlan)\n- [0.6.0](/ruby/docs/reference/google-cloud-bigquery-reservation-v1/0.6.0/Google-Cloud-Bigquery-Reservation-V1-CapacityCommitment-CommitmentPlan)\n- [0.5.0](/ruby/docs/reference/google-cloud-bigquery-reservation-v1/0.5.0/Google-Cloud-Bigquery-Reservation-V1-CapacityCommitment-CommitmentPlan)\n- [0.4.2](/ruby/docs/reference/google-cloud-bigquery-reservation-v1/0.4.2/Google-Cloud-Bigquery-Reservation-V1-CapacityCommitment-CommitmentPlan) \nReference documentation and code samples for the BigQuery Reservation V1 API module Google::Cloud::Bigquery::Reservation::V1::CapacityCommitment::CommitmentPlan.\n\nCommitment plan defines the current committed period. Capacity commitment\ncannot be deleted during it's committed period.\n\nConstants\n---------\n\n### COMMITMENT_PLAN_UNSPECIFIED\n\n**value:** 0 \nInvalid plan value. Requests with this value will be rejected with\nerror code `google.rpc.Code.INVALID_ARGUMENT`.\n\n### FLEX\n\n**value:** 3 \nFlex commitments have committed period of 1 minute after becoming ACTIVE.\nAfter that, they are not in a committed period anymore and can be removed\nany time.\n\n### FLEX_FLAT_RATE\n\n**value:** 7 \nSame as FLEX, should only be used if flat-rate commitments are still\navailable.\n\n### TRIAL\n\n**value:** 5 \nTrial commitments have a committed period of 182 days after becoming\nACTIVE. After that, they are converted to a new commitment based on the\n`renewal_plan`. Default `renewal_plan` for Trial commitment is Flex so\nthat it can be deleted right after committed period ends.\n\n### MONTHLY\n\n**value:** 2 \nMonthly commitments have a committed period of 30 days after becoming\nACTIVE. After that, they are not in a committed period anymore and can be\nremoved any time.\n\n### MONTHLY_FLAT_RATE\n\n**value:** 8 \nSame as MONTHLY, should only be used if flat-rate commitments are still\navailable.\n\n### ANNUAL\n\n**value:** 4 \nAnnual commitments have a committed period of 365 days after becoming\nACTIVE. After that they are converted to a new commitment based on the\nrenewal_plan.\n\n### ANNUAL_FLAT_RATE\n\n**value:** 9 \nSame as ANNUAL, should only be used if flat-rate commitments are still\navailable.\n\n### THREE_YEAR\n\n**value:** 10 \n3-year commitments have a committed period of 1095(3 \\* 365) days after\nbecoming ACTIVE. After that they are converted to a new commitment based\non the renewal_plan.\n\n### NONE\n\n**value:** 6 \nShould only be used for `renewal_plan` and is only meaningful if\nedition is specified to values other than EDITION_UNSPECIFIED. Otherwise\nCreateCapacityCommitmentRequest or UpdateCapacityCommitmentRequest will\nbe rejected with error code `google.rpc.Code.INVALID_ARGUMENT`. If the\nrenewal_plan is NONE, capacity commitment will be removed at the end of\nits commitment period."]]
