UpdateComputeQuotaSchedule - MaxCompute - Alibaba Cloud Documentation Center

This topic is generated by a machine translation engine without any human intervention. ALIBABA CLOUD DOES NOT GUARANTEE THE ACCURACY OF MACHINE TRANSLATED CONTENT. To request a human-translated version of this topic or provide feedback on this translation, please include it in the feedback form.

Update the time-based plan for computing quota.

Operation description

Please ensure that before using this interface, you have fully understood the Pricing and Billing of MaxCompute Elastic Reserved CU.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Debug

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

Operation: the value that you can use in the Action element to specify the operation on a resource.
Access level: the access level of each operation. The levels are read, write, and list.
Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- For mandatory resource types, indicate with a prefix of * .
- If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
Condition Key: the condition key that is defined by the cloud service.
Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.

Operation	Access level	Resource type	Condition key	Associated operation
odps:UpdateQuotaSchedule	update	*Quota `acs:odps:{#regionId}:{#accountId}:quotas/{#NickName}`	none	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 level-1 compute quota.	os_ComputeQuota_p
body	array<object>	No	The request body parameters.
	object	No
condition	object	No	The value of effective condition.
at	string	Yes	The start time when the quota plan takes effect.	10:00
timezone	string	No	Time zone. Note Default Key: UTC+8	UTC+8
type	string	Yes	The type of the quota plan. Notice Currently, only daily is supported.	daily
plan	string	Yes	The name of the quota plan.	planA

Notice When using, configuration should start from the effective time 00:00.

Response parameters

Parameter	Type	Description	Example
	object	The response parameters.
requestId	string	The request ID.	0be3e0aa16667684362147582e038f
httpCode	integer	HTTP status code. 1xx: Informational - The request has been received and is being processed. 2xx: Success - The request action was successfully received, understood, and accepted by the server. 3xx: Redirection - Further action must be taken to complete the request. 4xx: Client Error - The request contains an error in the request parameters, syntax, or specific request conditions cannot be met. 5xx: Server Error - The server could not fulfill the request due to other reasons.	200
errorCode	string	The error code.	QUOTA_PLAN_NOT_FOUND
errorMsg	string	The error message.	plan \"***\" does not exist
data	string	The data returned.	success

Examples

Sample success responses

JSONformat

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

Error codes

For a list of error codes, visit the Service error codes.

Change history

Change time	Summary of changes	Operation
2025-01-17	The request parameters of the API has changed	View Change Details