Modify MaxCompute Sub-Quota Settings via API - 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:UpdateSubQuotas

update

*Quota

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

None

Request syntax

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

Path Parameters

Parameter	Type	Required	Description	Example
nickname	string	Yes	The nickname of level-1 compute quota.	os_ComputeQuota_p

Request parameters

Parameter	Type	Required	Description	Example
body	object	No	The request body parameters.
subQuotaInfoList	array<object>	No	The list of level-2 quotas.
	array<object>	No	The list of level-2 quotas.
nickName	string	Yes	The nickname of the level-2 quota.	os_ComputeQuota
parameter	object	No	The parameters of the level-2 quota.
enablePriority	boolean	No	Specifies whether to enable the priority feature.	false
forceReservedMin	boolean	No	Specifies whether the quota is strongly exclusive.	false
maxCU	integer	Yes	The value of minCU in Reserved CUs. Note The value of maxCU must be less than or equal to the value of maxCU in the level-1 quota that you purchased.	50
minCU	integer	Yes	The value of maxCU in Reserved CUs. Note The total value of minCU in all the level-2 quotas is equal to the value of minCU in the level-1 quota. The value of minCU must be less than or equal to the value of maxCU in the level-2 quota and less than or equal to the value of minCU in the level-1 quota that you purchased.	50
schedulerType	string	No	Scheduling policy of the quota.	Fifo/Fair
singleJobCULimit	integer	No	The upper limit for CUs that can be concurrently used by a job scheduled to the quota.	10
type	string	No	The type of quota. Note FUXI_OFFLINE(default) : Quotas of this type are used to run batch jobs.	FUXI_OFFLINE

danger

The configuration submitted by UpdateComputeSubQuota is the final form of Quota;
UpdateComputeSubQuota must be configured with the default level-2 quota;
When the input parameter contains a non-existent level-2 quota, a new level-2 quota will be created;
If an existing level-2 quota is not declared in the input parameter, it will be deleted;
If the configuration parameters of the existing level-2 quota are inconsistent, the configuration of the level-2 quota will be updated.

Response elements

Element	Type	Description	Example
	object
requestId	string	The ID of the request.	0b57ff7616612271051086500ea3ce
httpCode	integer	The HTTP status code. 1xx: informational response. The request is received and is being processed. 2xx: success. The request is successfully received, understood, and accepted by the server. 3xx: redirection. The request is redirected, and further actions are required to complete the request. 4xx: client error. The request contains invalid request parameters or syntaxes, or specific request conditions cannot be met. 5xx: server error. The server cannot meet requirements due to other reasons.	200
errorCode	string	The error code.	OBJECT_NOT_EXIST
errorMsg	string	The error message.	this quota is not exist.
data	string	The returned result.	success

Examples

Success response

JSON format

{
  "requestId": "0b57ff7616612271051086500ea3ce",
  "httpCode": 200,
  "errorCode": "OBJECT_NOT_EXIST",
  "errorMsg": "this quota is not exist.",
  "data": "success"
}

Error codes

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.