1. Download the HBase TAR file. You can use one of the following methods to retrieve a TAR file:
- Method 1: Download the TAR file. This file includes all required enhanced dependencies. Click here to download and decompress the file. We recommend that you use this TAR file to retrieve all features of ApsaraDB for HBase Performance-enhanced Edition. Download and use the latest version of the TAR file alihbase-2.0.9-bin.tar.gz.
- Method 2: Download the TAR file from the HBase official website and decompress the TAR file to the
libdirectory. Then copy the JAR file of alihbase-connector to the same directory. For more information, see Install the SDK for Java.
2. Retrieve the Virtual Private Cloud (VPC) endpoint or the public endpoint for HBase Shell. For more information, see Connect to a cluster. You can refer to 'The endpoint used by Java API' section of the topic.
Add the following configuration to the hbase-site.xml file in the conf/ directory of the decompressed TAR file:
<configuration> <! -- The public endpoint or VPC internal endpoint used to connect the cluster. You can retrieve the endpoint on the Database Connection page in the console. --> <property> <name>hbase.zookeeper.quorum</name> <value>ld-xxxx-proxy-hbaseue.hbaseue.xxx.rds.aliyuncs.com:30020</value> </property> <! -- The default values for both the username and password parameters are root. You can change the username and password as needed. --> <property> <name>hbase.client.username</name> <value>root</value> </property> <property> <name>hbase.client.password</name> <value>root</value> </property> </configuration>
Use HBase Shell
Run the following command in the bin/ directory.
Now, you can run the native HBase Shell commands to connect to ApsaraDB for HBase
Performance-enhanced Edition. By default, the logs are stored in the
logs directory of the decompressed TAR file. For more information about how to use HBase
Shell, see HBase Shell. If you use HBase Shell to connect to ApsaraDB for HBase Performance-enhanced
Edition, you can manage tables and data by using some simple Data Definition Language
(DDL) and Data Manipulation Language (DML) statements. The cluster management commands
such as BALANCE and MOVE are disabled. For more information, see Limits.