This topic describes how to use a Kafka client demo to consume tracked data. The change tracking feature of the new version allows you to consume tracked data by using a Kafka client of V0.11 to V2.7.
- If you enable auto commit when you use the change tracking feature, some data may be committed before it is consumed. This results in data loss. We recommend that you manually commit data. Note If data fails to be committed, you can restart the client to continue consuming data from the last recorded consumption checkpoint. However, duplicate data may be generated during this period. You must manually filter out the duplicate data.
- Data is serialized and stored in the Avro format. For more information, see Record.avsc. Warning If you are not using the Kafka client that is described in this topic, you must parse the tracked data based on the Avro schema.
- The search unit is second when Data Transmission Service (DTS) calls the
offsetForTimesoperation. The search unit is millisecond when a native Kafka client calls this operation.
- Transient connections may occur between a Kafka client and the change tracking server due to several reasons, such as disaster recovery. If you are not using the Kafka client that is described in this topic, your Kafka client must have network reconnection capabilities.
Run the Kafka client
Download the Kafka client demo. For more information about how to use the demo, see Readme.
- Click and select Download ZIP to download the package.
- If you use a Kafka client of version 2.0, you must change the version number in the subscribe_example-master/javaimpl/pom.xml file to 2.0.0.
|Step||File or directory|
|1. Use the native Kafka consumer to obtain incremental data from the change tracking instance.||subscribe_example-master/javaimpl/src/main/java/recordgenerator/|
|2. Deserialize the image of the incremental data, and obtain the pre-image, post-image , and other attributes. |
|3. Convert the dataTypeNumber values in the deserialized data into data types of the corresponding database. |
Note For more information, see the following topics:
The following steps show how to run the Kafka client to consume tracked data. In this example, IntelliJ IDEA Community Edition 2018.1.4 for Windows is used.
- Create a change tracking task. For more information, see Track data changes from an ApsaraDB RDS for MySQL instance, Track data changes from a PolarDB for MySQL cluster, or Track data changes from a self-managed Oracle database.
- Create one or more consumer groups. For more information, see Create consumer groups.
- Download the Kafka client demo and decompress the package. Note Click and select Download ZIP to download the package.
- Open IntelliJ IDEA. In the window that appears, click Open.
- In the dialog box that appears, go to the directory in which the downloaded demo resides. Find the pom.xml file.
- In the dialog box that appears, select Open as Project.
- In the Project tool window of IntelliJ IDEA, expand folders to find the demo file of the Kafka client, and double-click the file. The file name is NotifyDemoDB.java.
- Configure the parameters in the NotifyDemoDB.java file.
Parameter Description Method to obtain USER_NAME The account of the consumer group.Warning If you are not using the Kafka client that is described in this topic, you must specify this parameter in the following format:
<Username>-<Consumer group ID>. Example:
dtstest-dtsae******bpv. Otherwise, the connection fails.
In the DTS console, click the instance ID. In the left-side navigation pane, click Consume Data. You can obtain the consumer group ID and the corresponding username.Note The password of the consumer group account is automatically specified when you create the consumer group. PASSWORD_NAME The password of the account. SID_NAME The ID of the consumer group. GROUP_NAME The name of the consumer group. Set this parameter to the consumer group ID. KAFKA_TOPIC The topic of the change tracking instance. In the DTS console, click the instance ID. On the Task Management page, you can obtain the tracked topic and the network information. KAFKA_BROKER_URL_NAME The endpoint of the change tracking instance.Note If you track data changes over internal networks, the network latency is minimal. This is applicable if the Elastic Compute Service (ECS) instance on which you deploy the Kafka client resides on the classic network or in the same virtual private cloud (VPC) as the change tracking instance. INITIAL_CHECKPOINT_NAME The consumption checkpoint of consumed data. The value is a UNIX timestamp. Example: 1592269238.Note
- You must save the consumption checkpoint for the following reasons:
- If the consumption process is interrupted, you can specify the consumption checkpoint on the change tracking client to resume data consumption. This prevents data loss.
- When you start the change tracking client, you can specify the consumption checkpoint to consume data on demand.
- If the SUBSCRIBE_MODE_NAME parameter is set to subscribe, the INITIAL_CHECKPOINT_NAME parameter that you specified takes effect only when you start the change tracking client for the first time.
The consumption checkpoint of consumed data must be within the data range of the change tracking instance, as shown in the following figure. The consumption checkpoint must be converted into a UNIX timestamp.Note You can use a search engine to obtain a UNIX timestamp converter. USE_CONFIG_CHECKPOINT_NAME Specifies whether to force the client to consume data from the specified consumption checkpoint. Default value: true. You can set this parameter to true to prevent the data that is received but not processed from being lost. N/A SUBSCRIBE_MODE_NAME Specifies whether to run two or more Kafka clients for a consumer group. If you want to use this feature, set this parameter to subscribe for these Kafka clients.
Default value: assign. The default value indicates that only one Kafka client is deployed.
- You must save the consumption checkpoint for the following reasons:
- In the top menu bar of IntelliJ IDEA, choose to run the client. Note If you run IntelliJ IDEA for the first time, a specific time period is required to load and install relevant dependencies.
Results on the Kafka client
The following figure shows that the Kafka client can track data changes from the source database.
You can delete the double forward slashes (
//) from the
//log.info(ret); string in line 25 of the NotifyDemoDB.java file. Then, run the client again to view the data change information.
- Q: Why do I need to record the consumption checkpoint of the Kafka client?
A: The consumption checkpoint recorded by DTS is the point in time when DTS receives a commit operation from the Kafka client. The recorded consumption checkpoint may be different from the actual consumption time. If a business application or the Kafka client is unexpectedly interrupted, you can specify an accurate consumption checkpoint to continue data consumption. This prevents data loss or duplicate data consumption.
Mappings between MySQL data types and dataTypeNumber values
|MySQL data type||Value of dataTypeNumber|
Mappings between Oracle data types and dataTypeNumber values
|Oracle data type||Value of dataTypeNumber|
|CHAR and NCHAR||96|
Mappings between PostgreSQL data types and dataTypeNumber values
|PostgreSQL data type||Value of dataTypeNumber|
|TIME/TIME WITHOUT TIME ZONE||1083|
|TIME WITH TIME ZONE||1266|
|TIMESTAMP/TIMESTAMP WITHOUT TIME ZONE||1114|
|TIMESTAMP WITH TIME ZONE||1184|