DescribeConfigVersionDifference - ApsaraDB for ClickHouse

Operation description

Note

This operation applies only to community-compatible clusters that were created after December 1, 2021.

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

clickhouse:DescribeConfigVersionDifference

get

*All Resource

*

None

Request parameters

Parameter	Type	Required	Description	Example
DBClusterId	string	Yes	The cluster ID. Call the DescribeDBClusters operation to query the IDs of all clusters in the destination region.	cc-bp1tm8zf130ew****
ChangeId	string	Yes	The ID of the change record. Call the DescribeConfigHistory operation to query the IDs of change records.	1

Response elements

Element	Type	Description	Example
	object	Schema of Response
RequestId	string	The request ID.	D0CEC6AC-7760-409A-A0D5-E6CD8660E9CC
OldConfigXML	string	The configuration parameters before the change.	" 300 4096 debug 1000M 5368709120 150 4096 0 0 256 auto 100 1 1717986918 "
NewConfigXML	string	The configuration parameters after the change.	" 400 4096 debug 1000M 5368709120 201 4096 0 0 256 auto 100 1 1717986918 "

Examples

Success response

JSON format

{
  "RequestId": "D0CEC6AC-7760-409A-A0D5-E6CD8660E9CC",
  "OldConfigXML": "\"\n\n    300\n    4096\n    \n        debug\n        1000M\n    \n    5368709120\n    150\n    4096\n    0\n    0\n    \n        256\n        auto\n        100\n        1\n    \n    1717986918\n\"",
  "NewConfigXML": "\"\n\n    400\n    4096\n    \n        debug\n        1000M\n    \n    5368709120\n    201\n    4096\n    0\n    0\n    \n        256\n        auto\n        100\n        1\n    \n    1717986918\n\""
}

Error codes

HTTP status code	Error code	Error message	Description
400	IdempotentParameterMismatch	The request uses the same client token as a previous, but non-identical request. Do not reuse a client token with different requests, unless the requests are identical.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.