Queries a list of databases, tables, and columns in an AnalyticDB for MySQL cluster.
Operation description
- Regional public endpoint:
adb.<region-id>.aliyuncs.com
. Example:adb.cn-hangzhou.aliyuncs.com
. - Regional Virtual Private Cloud (VPC) endpoint:
adb-vpc.<region-id>.aliyuncs.com
. Example:adb-vpc.cn-hangzhou.aliyuncs.com
.
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:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level,
All Resources
is 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 |
---|---|---|---|---|
adb:describeAllDataSource | get |
|
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
RegionId | string | Yes | The region ID. | cn-hangzhou |
DBClusterId | string | Yes | The ID of the AnalyticDB for MySQL Data Lakehouse Edition cluster. | amv-bp1pke2pcfavw**** |
SchemaName | string | No | The name of the database. | adb_demo |
TableName | string | No | The name of the table. | test |
Response parameters
Examples
Sample success responses
JSON
format
{
"RequestId": "C7EDB8E4-9769-4233-88C7-DCA4C9******",
"Tables": {
"Table": [
{
"TableName": "test",
"DBClusterId": "amv-bp1pke2pcfavw****",
"SchemaName": "adb_demo"
}
]
},
"Columns": {
"Column": [
{
"Type": "bigint",
"ColumnName": "id",
"TableName": "test",
"AutoIncrementColumn": true,
"DBClusterId": "amv-bp1pke2pcfavw****",
"PrimaryKey": false,
"SchemaName": "adb_demo"
}
]
},
"Schemas": {
"Schema": [
{
"DBClusterId": "amv-bp1pke2pcfavw****",
"SchemaName": "adb_demo"
}
]
}
}
Error codes
HTTP status code | Error code | Error message | Description |
---|---|---|---|
400 | MDS.IllegalArgument | Invalid argument. | An invalid parameter is used. |
400 | MDS.InvalidPrivilege | No permissions. | You are not authorized to perform this operation. |
400 | MDS.MetaSchemaAlreadyExist | The database already exists. | The specified database already exists. |
400 | MDS.MetaSchemaNotExist | The database does not exist. | The specified database does not exist. |
400 | MDS.MetaTableAlreadyExist | The table already exists. | The specified table already exists. |
400 | MDS.MetaTableNotExist | The table is not found. | The specified table does not exist. |
500 | MDS.InternalError | An internal MDS error occurred. | An internal error occurred. |
500 | MDS.MetaVisitError | Failed to access metadata. | Failed to access the metadata. |
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation |
---|---|---|
2023-10-18 | The Error code has changed | View Change Details |
2023-08-25 | The Error code has changed | View Change Details |
2023-08-22 | The Error code has changed | View Change Details |