This topic describes the basic information and usage notes of ApsaraDB for HBase API.
For more information about how to call API operations in OpenAPI Explorer, see Overview.
Basic information
Versions
Version | Description |
2019-01-01 | Recommended. |
Endpoints
Select an endpoint based on the region where your cluster is deployed to reduce latency.
For example, the ApsaraDB for HBase endpoint for the China (Qingdao) region is hbase.aliyuncs.com. For more information about endpoints, see Request Structure.
User identities
User identity | Supported |
Yes | |
RAM user (recommended) | Yes |
RAM role (recommended) | Yes |
API styles
ApsaraDB for HBase API operations are called in the remote procedure call (RPC) style. For more information about the API styles, see API styles.
Call methods
Call method | Supported | Description |
Alibaba Cloud SDKs (recommended) | Yes | For more information about the programming languages that are supported by ApsaraDB for HBase SDKs and the methods to install dependencies, see ApsaraDB for HBase SDKs. |
Yes | N/A. | |
Yes | N/A. | |
Yes | N/A. |
If none of the preceding methods meet your business requirements, you can encapsulate API requests to call API operations. This method is not recommended. For more information, see Custom encapsulation.
Usage notes
If an error is returned after you call an API operation, you can check whether the values of the request parameters are valid based on the returned error code. For more information, see ApsaraDB for HBase - Error Codes.
You can also use the Alibaba Cloud OpenAPI Diagnostics platform to perform self-service diagnostics based on the returned request ID or SDK error information.