DescribeConfigVersionDifference - ApsaraDB for ClickHouse

Queries the values of the configuration parameters of an ApsaraDB for ClickHouse cluster before and after the values of the configuration parameters are changed.

Operation description

Note You can call this operation only for ApsaraDB for ClickHouse clusters that were created after December 1, 2021.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

Debug

Authorization information

There is currently no authorization information disclosed in the API.

Request parameters

Parameter	Type	Required	Description	Example
DBClusterId	string	Yes	The cluster ID. You can call the DescribeDBClusters operation to query information about all the clusters that are deployed in a specific region. The information includes the cluster IDs.	cc-bp1tm8zf130ew****
ChangeId	string	Yes	The ID of the change record. You can call the DescribeConfigHistory operation to query the ID of the change record.	1

Response parameters

Parameter	Type	Description	Example
	object	Schema of Response
RequestId	string	The request ID.	D0CEC6AC-7760-409A-A0D5-E6CD8660E9CC
OldConfigXML	string	The values of the configuration parameters before the values of the configuration parameters are changed.	"<?xml version="1.0"?> <yandex> <keep_alive_timeout>300</keep_alive_timeout> <listen_backlog>4096</listen_backlog> <logger> <level>debug</level> <size>1000M</size> </logger> <mark_cache_size>5368709120</mark_cache_size> <max_concurrent_queries>150</max_concurrent_queries> <max_connections>4096</max_connections> <max_partition_size_to_drop>0</max_partition_size_to_drop> <max_table_size_to_drop>0</max_table_size_to_drop> <merge_tree> <max_delay_to_insert>256</max_delay_to_insert> <max_part_loading_threads>auto</max_part_loading_threads> <max_suspicious_broken_parts>100</max_suspicious_broken_parts> <zookeeper_session_expiration_check_period>1</zookeeper_session_expiration_check_period> </merge_tree> <uncompressed_cache_size>1717986918</uncompressed_cache_size> </yandex>"
NewConfigXML	string	The values of the configuration parameters after the values of the configuration parameters are changed.	"<?xml version="1.0"?> <yandex> <keep_alive_timeout>400</keep_alive_timeout> <listen_backlog>4096</listen_backlog> <logger> <level>debug</level> <size>1000M</size> </logger> <mark_cache_size>5368709120</mark_cache_size> <max_concurrent_queries>201</max_concurrent_queries> <max_connections>4096</max_connections> <max_partition_size_to_drop>0</max_partition_size_to_drop> <max_table_size_to_drop>0</max_table_size_to_drop> <merge_tree> <max_delay_to_insert>256</max_delay_to_insert> <max_part_loading_threads>auto</max_part_loading_threads> <max_suspicious_broken_parts>100</max_suspicious_broken_parts> <zookeeper_session_expiration_check_period>1</zookeeper_session_expiration_check_period> </merge_tree> <uncompressed_cache_size>1717986918</uncompressed_cache_size> </yandex>"

Examples

Sample success responses

JSONformat

{
  "RequestId": "D0CEC6AC-7760-409A-A0D5-E6CD8660E9CC",
  "OldConfigXML": "\"<?xml version=\"1.0\"?>\n<yandex>\n    <keep_alive_timeout>300</keep_alive_timeout>\n    <listen_backlog>4096</listen_backlog>\n    <logger>\n        <level>debug</level>\n        <size>1000M</size>\n    </logger>\n    <mark_cache_size>5368709120</mark_cache_size>\n    <max_concurrent_queries>150</max_concurrent_queries>\n    <max_connections>4096</max_connections>\n    <max_partition_size_to_drop>0</max_partition_size_to_drop>\n    <max_table_size_to_drop>0</max_table_size_to_drop>\n    <merge_tree>\n        <max_delay_to_insert>256</max_delay_to_insert>\n        <max_part_loading_threads>auto</max_part_loading_threads>\n        <max_suspicious_broken_parts>100</max_suspicious_broken_parts>\n        <zookeeper_session_expiration_check_period>1</zookeeper_session_expiration_check_period>\n    </merge_tree>\n    <uncompressed_cache_size>1717986918</uncompressed_cache_size>\n</yandex>\"",
  "NewConfigXML": "\"<?xml version=\"1.0\"?>\n<yandex>\n    <keep_alive_timeout>400</keep_alive_timeout>\n    <listen_backlog>4096</listen_backlog>\n    <logger>\n        <level>debug</level>\n        <size>1000M</size>\n    </logger>\n    <mark_cache_size>5368709120</mark_cache_size>\n    <max_concurrent_queries>201</max_concurrent_queries>\n    <max_connections>4096</max_connections>\n    <max_partition_size_to_drop>0</max_partition_size_to_drop>\n    <max_table_size_to_drop>0</max_table_size_to_drop>\n    <merge_tree>\n        <max_delay_to_insert>256</max_delay_to_insert>\n        <max_part_loading_threads>auto</max_part_loading_threads>\n        <max_suspicious_broken_parts>100</max_suspicious_broken_parts>\n        <zookeeper_session_expiration_check_period>1</zookeeper_session_expiration_check_period>\n    </merge_tree>\n    <uncompressed_cache_size>1717986918</uncompressed_cache_size>\n</yandex>\""
}

Error codes

HTTP status code	Error code	Error message
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.

For a list of error codes, visit the Service error codes.

Change history

Change time	Summary of changes	Operation
2022-09-22	Add Operation	View Change Details