All Products
Search

This Product

    MaxCompute:UpdateComputeQuotaPlan - 更新Quota计划

    Document Center

    MaxCompute:UpdateComputeQuotaPlan - 更新Quota计划

    Last Updated:Aug 20, 2026

    更新Quota计划。

    Operation description

    请确保在使用该接口前，已充分了解 MaxCompute 弹性预留 CU 的收费方式和价格。

    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:UpdateQuotaPlan

    update

    *Quota

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

    		 None None

    Request syntax

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

    Path Parameters

    Parameter

    Type

    Required

    Description

    Example
    nickname

    string

    Yes

    一级 Quota 昵称。

    os_ComputeQuota_p

    Request parameters

    Parameter

    Type

    Required

    Description

    Example
    body

    object

    No

    请求体参数。

    name

    string

    Yes

    Quota 计划名称。

    planA
    quota

    object

    No

    Quota 属性。

    parameter

    object

    No

    一级 Quota 属性。

    elasticReservedCU

    integer

    Yes

    一级 Quota 弹性预留 CU 值。

    Note

    • 一级 Quota ElasticReservedCU 必须是 50 倍数

    • 一级 Quota ElasticReservedCU 大于等于 0

    • 一级 Quota ElasticReservedCU 小于等于一级 Quota MaxCU

    50
    subQuotaInfoList

    array<object>

    No

    二级 Quota 列表。

    array<object>

    No

    二级 Quota 列表。

    nickName

    string

    Yes

    二级 quota 昵称。

    os_ComputeQuota
    parameter

    object

    No

    二级 Quota 属性。

    elasticReservedCU

    integer

    Yes

    弹性预留 CU 值。

    Note

    • 二级 Quota 的 ElasticReservedCU 大于等于 0

    • 二级 Quota 的 ElasticReservedCU 总和必须等于一级 Quota ElasticReservedCU

    50
    maxCU

    integer

    Yes

    预留 CU 上限。

    Note

    • 二级 Quota 的 maxCU 不能超过一级 Quota 的 maxCU。

    50
    minCU

    integer

    Yes

    预留 CU 保障。

    Note

    • 所有二级 Quota minCU 总和需要等于 一级 Quota 的 minCU

    • 二级 Quota 的 minCU 不能超过自身的 maxCU

    50
    danger

    • 该接口仅支持计算类型 Quota

    • subQuotaInfoList 内需要列出所有二级 Quota

    • 必须配置默认二级 Quota , 默认二级 Quota 名称一般为 一级 Quota Nickname 去除 _p 。例如 os_ComputeQuota_p 的默认二级 Quota 为 os_ComputeQuota

    Response elements

    Element

    Type

    Description

    Example

    object

    请求返回参数。

    requestId

    string

    请求 ID。

    0be3e0aa16667684362147582e038f
    httpCode

    integer

    HTTP 状态码。

    • 1xx：信息响应 - 请求已接收，正在处理中。

    • 2xx：成功 - 请求动作已被服务端成功接收、理解并接受。

    • 3xx：重定向 - 请求被重定向，采取进一步行动以完成请求。

    • 4xx：客户端错误 - 请求包含错误请求参、语法或特定请求条件无法满足。

    • 5xx：服务端错误 - 服务器由于其他原因无法满足请求。

    200
    errorCode

    string

    错误码。

    QUOTA_PLAN_NOT_FOUND
    errorMsg

    string

    错误信息。

    plan \"***\" does not exist
    data

    string

    返回结果。

    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 Error Codes for a complete list.

    Release notes

    See Release Notes for a complete list.