Use the UpdateQuotaSchedule API to update a quota scheduling plan - MaxCompute - Alibaba Cloud - MaxCompute

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

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}/schedule HTTP/1.1

Path Parameters

Parameter	Type	Required	Description	Example
nickname	string	Yes	The quota name.	%E9%BB%98%E8%AE%A4%E9%A2%84%E4%BB%98%E8%B4%B9Quota_p #中文名称需要经过utf8 urlencode编码转义

Request parameters

Parameter	Type	Required	Description	Example
tenantId	string	No	The tenant ID.	478403690625249
region	string	No	The region ID.	cn-chengdu
body	string	No	The request body.	# 立即生效 [ { "type": "once", "plan": "planA", "operator":"userA" } ] # 定时调度 [ { "id": "etl_time", "type": "daily", "condition": { "at": "0800" }, "plan": "planA" }, { "id": "bi", "type": "daily", "condition": { "at": "0900" }, "plan": "planB" }, ]

Response elements

Element	Type	Description	Example
	object	PopResult
requestId	string	The request ID.	0a06dfe516691014920015940e1c9d
data	string	The response result.	success

Examples

Success response

JSON format

{
  "requestId": "0a06dfe516691014920015940e1c9d",
  "data": "success"
}

Error codes

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.