Read data from DataHub and write data to ApsaraDB for HBase

Develop a job

1. Download and decompress the Hbase_Demo-master.zip package to your on-premises machine.
2. In IntelliJ IDEA, choose File > Open to open the decompressed packeage Hbase_Demo-master.
3. Double-click the HbaseDemo.java file in the \Hbase_Demo-master\src\main\java directory. Then, configure the parameters related to DataHub and ApsaraDB for HBase in the HbaseDemo.java file.

   // Configure the parameters related to DataHub.
   //private static String endPoint ="public endpoint";// Access DataHub over the Internet. If you enter an internal endpoint, you do not need to enter the public endpoint. 
   private static String endPoint = "inner endpoint";// Access DataHub over an internal network. 
   private static String projectName = "yourProject";
   private static String topicSourceName = "yourTopic";
   private static String accessId = "yourAK";
   private static String accessKey = "yourAS";
   private static Long datahubStartInMs = 0L;// Set the time that corresponds to the start offset. 
   // Configure the parameters related to ApsaraDB for HBase.
   private static String zkQuorum = "yourZK";
   private static String tableName = "yourTable";
   private static String columnFamily = "yourcolumnFamily";

4. Go to the directory where the pom.xml file is stored. Then, run the following command to package the file:

   mvn package -Dcheckstyle.skip

   A Java Archive (JAR) package named Hbase_Demo-1.0-SNAPSHOT-shaded.jar appears in the target directory, based on the artifactId parameter that you configured in the pom.xml file for your project. This indicates that job development is complete.

Publish a job

-- Required. The full name of the main class. 
blink.main.class=Hbase_Demo.HbaseDemo

-- The name of the job. 
blink.job.name=datahub_demo

-- The resource name of the JAR package that contains the full name of the main class. If multiple JAR packages exist, you must specify this parameter. 
--blink.main.jar=Hbase_Demo-1.0-snapshot.jar

-- The default state backend configuration. This field takes effect when the job code is not explicitly configured. 
state.backend.type=niagara
state.backend.niagara.ttl.ms=129600000

-- The default checkpoint configuration. The configuration takes effect when the job code is not explicitly configured. 
blink.checkpoint.interval.ms=180000

Verify the test results

1. Send test data to DataHub in the Realtime Compute for Apache Flink console.

   CREATE TABLE kafka_src (
      a BOOLEAN
   ) WITH (
      type = 'random'
   );
   
   CREATE TABLE event_logs (
      `a` BOOLEAN,
       b  VARCHAR,
      `c` VARCHAR
   ) WITH (
       type = 'datahub',
       endPoint = '<yourEndpoint>',
       project = '<yourProject>',
       topic = '<yourTopic>',
       accessId='<yourAccessId>',    
       accessKey='<yourAccessKey>'
   );
   
   INSERT INTO event_logs
   SELECT
       a,'rowkey3' as b,'123' as c
   FROM kafka_src;

2. Connect to the ApsaraDB for HBase cluster.For more information about how to connect to an ApsaraDB for HBase cluster, see Use HBase Shell to access ApsaraDB for HBase.
3. Run the scan 'hbase_sink' command to query the data written to ApsaraDB for HBase.
   If information similar to that in the following figure appears, Realtime Compute for Apache Flink writes the DataHub data to ApsaraDB for HBase.

FAQ

java.lang.AbstractMethodError:com.alibaba.fastjson.support.jaxrs.FastJsonAutoDiscoverable.configure(Lcom/alibaba/blink/shaded/datahub/javax/ws/rs/core/FeatureContext;)

<relocations combine.self="override">
   <relocation>
       <pattern>org.glassfish.jersey</pattern>
       <shadedPattern>com.alibaba.blink.shaded.datahub.org.glassfish.jersey</shadedPattern>
   </relocation>
</relocations>