You can use open source Flink or Realtime Compute for Apache Flink to access an ApsaraDB for HBase Performance-enhanced Edition cluster. This topic describes how to use open source Flink or Realtime Compute for Apache Flink to access an ApsaraDB for HBase Performance-enhanced Edition cluster.

Background information

You can create a table of an ApsaraDB for HBase Performance-enhanced Edition cluster, use the table as a dimension table or result table in Flink, and access the ApsaraDB for HBase performance-enhanced Edition cluster by using SQL statements or DataStream in Flink.

Prerequisites

  • If you use open source Flink to access an ApsaraDB for HBase Performance-enhanced Edition cluster, the version of the ApsaraDB for HBase Performance-enhanced Edition cluster must be 2.4.3 or later. If you use Realtime Compute for Apache Flink to access an ApsaraDB for HBase Performance-enhanced Edition cluster, the version of the ApsaraDB for HBase Performance-enhanced Edition cluster is unlimited. For more information about how to view or update the current version, see Minor version updates.
  • The IP address of a client is added to the whitelist of the ApsaraDB for HBase Performance-enhanced Edition cluster. For more information, see Configure IP address allowlists and security groups.
  • The Java API endpoint of the ApsaraDB for HBase Performance-enhanced Edition cluster is available.
    Note When you execute a DDL statement to create an ApsaraDB for HBase table as a dimension table or result table in Flink, you must use the Java API endpoint as the endpoint in the DDL statement.
  • You are granted the read and write permissions on the Flink table. For more information about how to grant permissions, see Manage permissions.

Usage notes

  • To access the ApsaraDB for HBase Performance-enhanced Edition cluster over the Internet, replace the open source HBase client with the ApsaraDB for HBase client before you perform the data access operation. For more information, see Use ApsaraDB for HBase SDK for Java to replace an open source HBase version with an ApsaraDB for HBase version.
  • If applications are deployed on an Elastic Compute Service (ECS) instance and you want to access the ApsaraDB for HBase Performance-enhanced Edition cluster over a virtual private cloud (VPC), make sure that the ApsaraDB for HBase Performance-enhanced Edition cluster and the ECS instance meet the following requirements to ensure network connectivity:
    • The ApsaraDB for HBase Performance-enhanced cluster and the ECS instance are deployed in the same region. We recommend that you deploy the cluster and the instance in the same zone to reduce network latency.
    • The ApsaraDB for HBase Performance-enhanced Edition cluster and the ECS instance belong to the same VPC.
  • If you use open source Flink to access the ApsaraDB for HBase Performance-enhanced Edition cluster, you can access only ApsaraDB for HBase tables that are created by using HBaseue Shell. This limit does not take effect if you use Realtime Compute for Apache Flink.

Create a dimension table

  • You can create a dimension table and use open source Flink to access the ApsaraDB for HBase Performance-enhanced Edition cluster. For more information, see Create a dimension table.
  • You can create a dimension table and use Realtime Compute for Apache Flink to access the ApsaraDB for HBase Performance-enhanced cluster. For more information, see Create an ApsaraDB for HBase dimension table.

Create a result table

  • You can create a result table and use open source Flink to access the ApsaraDB for HBase Performance-enhanced Edition cluster. For more information, see Create a result table.
  • You can create a result table and use Realtime Compute for Apache Flink to access the ApsaraDB for HBase Performance-enhanced cluster. For more information, see Create an ApsaraDB for HBase result table.