Updates the basic configuration of a MaxCompute quota. For example, you can call this operation to add or delete a level-2 quota, define the basic attributes of a level-2 quota, and define the configuration of compute units (CUs) for a quota plan that is in effect.
Debugging
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 Resourcesis 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:UpdateSubQuotas | update | *Quota acs:odps:{#regionId}:{#accountId}:quotas/{#NickName} |
| none |
Request syntax
PUT /api/v1/quotas/{nickname}/computeSubQuota HTTP/1.1
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| nickname | string | Yes | The nickname of level-1 compute quota. | os_ComputeQuota_p |
| body | object | No | The request body parameters. | |
| subQuotaInfoList | array<object> | No | The list of level-2 quotas. | |
| 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 | long | 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 | long | Yes | The value of maxCU in Reserved CUs. Note
| 50 |
| schedulerType | string | No | Scheduling policy of the quota. | Fifo/Fair |
| singleJobCULimit | long | 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 |
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 parameters
Examples
Sample success responses
JSONformat
{
"requestId": "0b57ff7616612271051086500ea3ce",
"httpCode": 200,
"errorCode": "OBJECT_NOT_EXIST",
"errorMsg": "this quota is not exist.",
"data": "success"
}Error codes
For a list of error codes, visit the Service error codes.