UpdateComputeQuotaSchedule-阿里云帮助中心

Updates the time-based schedule for a computing quota.

Operation description

Before you call this operation, ensure that you understand the billing methods and pricing of reserved compute units (CUs) in MaxCompute.

Try it now

您可以在OpenAPI Explorer中直接运行该接口，免去您计算签名的困扰。运行成功后，OpenAPI Explorer可以自动生成SDK代码示例。

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.
API: The API that you can call to perform the action.
Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.
Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.
- For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.
- For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.
Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.
Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

odps:UpdateQuotaSchedule

update

*Quota

acs:odps:{#regionId}:{#accountId}:quotas/{#NickName}

None

Request syntax

PUT /api/v1/quotas/{nickname}/computeQuotaSchedule HTTP/1.1

Request parameters

Parameter	Type	Required	Description	Example
nickname	string	Yes	The nickname of the level-1 quota.	os_ComputeQuota_p
body	array<object>	No	The request body parameters.
	array<object>	No	The request body parameters.
condition	object	No	The condition for the plan to take effect.
at	string	Yes	The time when the plan takes effect.	10:00
type	string	Yes	The type. Important Only daily is supported.	daily
plan	string	Yes	The name of the quota plan.	planA
scheduleTimezone	string	No	The time zone. Note The default value is UTC+8.	UTC+8

Important

You must configure the plan to start at 00:00.

Response elements

Element	Type	Description	Example
	object	The parameters that are returned for the request.
requestId	string	The request ID.	0be3e0aa16667684362147582e038f
httpCode	integer	The HTTP status code. 1xx: an informational response. The request was received and is being processed. 2xx: a success response. The request was successfully received, understood, and accepted by the server. 3xx: a redirection response. The request was redirected. You must take further action to complete the request. 4xx: a client error. The request contains invalid request parameters or syntax, or cannot be fulfilled for a specific reason. 5xx: a server error. The server cannot fulfill the request for other reasons.	200
errorCode	string	The error code.	QUOTA_PLAN_NOT_FOUND
errorMsg	string	The error message.	plan \"***\" does not exist
data	string	The returned result.	success

Examples

Success response

JSON format

{
  "requestId": "0be3e0aa16667684362147582e038f",
  "httpCode": 200,
  "errorCode": "QUOTA_PLAN_NOT_FOUND",
  "errorMsg": "plan \\\"***\\\" does not exist",
  "data": "success"
}

Error codes

See for a complete list.

Release notes

See 变更详情 for a complete list.