Use DataWorks to run a full import of data into LindormTable from an existing relational database. This topic walks you through creating the required DataWorks workspace, resource group, and network configuration, then setting up and publishing an offline sync task.
When to use this approach: Use DataWorks when you need to perform a one-time or scheduled full copy of data from a supported source database.
Supported source databases: MySQL, PolarDB, PostgreSQL, Oracle, SQL Server, and Cassandra.
Prerequisites
Before you begin, ensure that you have:
Added the client IP address to the Lindorm whitelist
Usage notes
Public network access or single-node instance: If you access Lindorm over the public network or use a single-node Lindorm instance, upgrade the SDK and update the configuration before following this topic. See Step 1 in Connect to and use LindormTable through the HBase Java API.
ECS-hosted applications: If your application runs on an Elastic Compute Service (ECS) instance, the ECS instance and the Lindorm instance must be in the same region and the same virtual private cloud (VPC). Place them in the same zone for lower network latency. These requirements ensure network connectivity between DataWorks and your Lindorm instance.
Step 1: Create a workspace
Create a workspace in DataWorks. The workspace is where you manage your data development tasks and configurations.
Step 2: Create a resource group
A resource group allocates compute resources within your account and controls access. Choose the resource group type based on your network setup.
| Resource group type | Notes | Reference |
|---|---|---|
| Exclusive resource group | Cannot be used across regions — an exclusive resource group in China (Shanghai) only works with workspaces in that same region and cannot access a Lindorm cluster across vSwitches. | Exclusive resource group mode |
| Default resource group | Accessing Lindorm over the public network incurs additional fees in DataWorks. | — |
Step 3: Configure the network
Configure network connectivity between DataWorks and your Lindorm instance. The steps differ depending on which resource group type you created.
Exclusive resource group
On the Instance Details page of the Lindorm instance, get the VPC of the instance.
Attach the DataWorks exclusive resource group to the VPC of the Lindorm instance.
In the VPC console, get the IPv4 CIDR block of the VPC and vSwitch attached to the DataWorks exclusive resource group.
Add the IPv4 CIDR block to the Lindorm whitelist.
Default resource group
Get the IP addresses for the default resource group by following Add a whitelist in the DataWorks documentation. Add the IP addresses that correspond to your region to the Lindorm whitelist.
Step 4: Create a sync task
Create a data import offline sync task in DataWorks.
Step 5: Modify the task configuration
The configuration model depends on how you access Lindorm:
| Access method | Model | Reader configuration | Writer configuration |
|---|---|---|---|
| Lindorm SQL | TableService | Lindorm data source (reader) | Lindorm data source (writer) |
| HBase-compatible mode | WideColumn | Lindorm data source (reader) | Lindorm data source (writer) |
The lindorm.client.seedserver parameter in the sample script specifies the HBase Java API-compatible endpoint for LindormTable.
Step 6: Submit and publish the task
To run the task on a schedule, publish it to the production environment. For more information, see Publish a task.