All Products
Search

This Product

    Elasticsearch:Use DataWorks to synchronize data from Hadoop to Alibaba Cloud Elasticsearch

    Document Center

    Elasticsearch:Use DataWorks to synchronize data from Hadoop to Alibaba Cloud Elasticsearch

    Last Updated:Apr 28, 2024

    When you use Hadoop to perform interactive big data analytics and queries, the process may be time-consuming. To address this issue, you can synchronize data from Hadoop to Alibaba Cloud Elasticsearch for analytics and queries. Elasticsearch can respond to multiple types of queries within seconds, especially ad hoc queries. This topic describes how to use the Data Integration service of DataWorks to quickly synchronize data from Hadoop to Alibaba Cloud Elasticsearch.

    Background information

    DataWorks is an end-to-end big data development and governance platform based on big data compute engines. DataWorks provides features such as data development, task scheduling, and data management. The Data Integration service of DataWorks can collect offline data at a minimum interval of 5 minutes. You can create batch synchronization tasks in DataWorks to rapidly synchronize data from various data sources to Alibaba Cloud Elasticsearch in offline mode.

    • The following types of data sources are supported:

      • Alibaba Cloud databases: ApsaraDB RDS for MySQL, ApsaraDB RDS for PostgreSQL, ApsaraDB RDS for SQL Server, ApsaraDB for MongoDB, and ApsaraDB for HBase

      • Alibaba Cloud PolarDB for Xscale (PolarDB-X) (formerly DRDS)

      • Alibaba Cloud MaxCompute

      • Alibaba Cloud Object Storage Service (OSS)

      • Alibaba Cloud Tablestore

      • Self-managed databases: HDFS, Oracle, FTP, Db2, MySQL, PostgreSQL, SQL Server, MongoDB, and HBase

    • The following synchronization scenarios are supported:

      • Synchronize big data to Alibaba Cloud Elasticsearch in offline mode.

      • Synchronize all data in a table to Alibaba Cloud Elasticsearch.

    Prerequisites

    Note

    • A Hadoop cluster exists and contains data.

    • The Hadoop cluster, Elasticsearch cluster, and DataWorks workspace must reside in the same region.

    • The Hadoop cluster, Elasticsearch cluster, and DataWorks workspace must be in the same time zone. Otherwise, if you synchronize time-related data, the data in the source and the data in the destination after the synchronization may have a time zone difference.

    Billing

    Procedure

    Step 1: Create an exclusive resource group for Data Integration

    Create an exclusive resource group for Data Integration, and associate the resource group with a virtual private cloud (VPC) and the created workspace. Exclusive resource groups ensure fast and stable data transmission.

    1. Log on to the DataWorks console.

    2. In the top navigation bar, select a region. In the left-side navigation pane, click Resource Groups.

    3. On the Exclusive Resource Groups tab of the Resource Groups page, click Create Resource Group for Data Integration.

    4. On the DataWorks Exclusive Resources page, set Type to Exclusive Resource Groups for Data Integration, configure Resource Group Name, and then click Buy Now.

      For more information, see Create an exclusive resource group for Data Integration.

    5. On the Exclusive Resource Groups tab, find the newly created resource group and click Network Settings in the Actions column to associate the resource group with a VPC. For more information, see Associate the exclusive resource group for Data Integration with a VPC.

      Note

      In this example, an exclusive resource group for Data Integration is used to synchronize data over a VPC. For information about how to use an exclusive resource group for Data Integration to synchronize data over the Internet, see Add the EIP or CIDR block of an exclusive resource group for Data Integration to an IP address whitelist of a data source.

      The exclusive resource group must be connected to the VPC where the Hadoop cluster resides and the VPC where the Elasticsearch cluster resides. This way, data can be synchronized based on the exclusive resource group. Therefore, you must associate the exclusive resource group with the VPC, zone, and vSwitch of the Hadoop cluster and with those of the Elasticsearch cluster. For information about how to view the VPC, zone, and vSwitch of the Elasticsearch cluster, see View the basic information of a cluster.

      Important

      After you associate the exclusive resource group with the VPCs, you need to add the CIDR blocks of the vSwitches to which the Hadoop cluster and the Elasticsearch cluster belong to the private IP address whitelists of the Hadoop cluster and Elasticsearch cluster. For more information, see Configure a public or private IP address whitelist for an Elasticsearch cluster.

    6. Click the back icon in the upper-left corner of the page to return to the Resource Groups page.

    7. On the Exclusive Resource Groups tab, find the resource group and click Change Workspace in the Actions column to associate the resource group with the created workspace.

      For more information, see Associate the exclusive resource group for Data Integration with a workspace.

    Step 2: Add data sources

    1. Go to the Data Integration page.

      1. Log on to the DataWorks console.

      2. In the left-side navigation pane, click Workspaces.

      3. Find the workspace and choose Shortcuts > Data Integration in the Actions column.

    2. In the left-side navigation pane of the Data Integration page, click Data Source.

    3. Add a Hadoop data source.

      1. On the Data Sources page, click Add Data Source.

      2. In the Add Data Source dialog box, search for and select HDFS.

      3. In the Add HDFS Data Source dialog box, configure the parameters.

        For more information, see Add an HDFS data source.

      4. Find the resource group in the resource group list in the lower part of the dialog box and click Test Connectivity. If Connected is displayed, the resource group is connected to the Hadoop data source.

      5. Click Complete.

    4. Add an Elasticsearch data source in the same way. For more information, see Add an Elasticsearch data source.

    Step 3: Configure and run a batch synchronization task

    The exclusive resource group is used to run the batch synchronization task. The resource group obtains data from the source and writes the data to the Elasticsearch cluster.

    Note

    You can use the codeless UI or code editor to configure the batch synchronization task. In this example, the codeless UI is used. For information about how to use the code editor to configure the batch synchronization task, see Configure a batch synchronization task by using the code editor and Elasticsearch Writer.

    1. Go to the DataStudio page of DataWorks.

      1. Log on to the DataWorks console.

      2. In the left-side navigation pane, click Workspaces.

      3. Find the workspace and choose Shortcuts > Data Development in the Actions column.

    2. Create a batch synchronization task.

      1. In the left-side navigation pane, choose Create > Create Workflow to create a workflow.

      2. Right-click the name of the newly created workflow and choose Create Node > Offline synchronization.

      3. In the Create Node dialog box, configure the Name parameter and click Confirm.

    3. Configure the network and resources.

      1. For the source part, set Source to HDFS and Data Source Name to the name of the added Hadoop data source.

      2. For the resource group part, select the created exclusive resource group.

      3. For the destination part, set Destination to Elasticsearch and Data Source Name to the name of the added Elasticsearch data source.

    4. Click Next.

    5. Configure the task.

      1. In the Source section, select the table whose data you want to synchronize.

      2. In the Destination section, configure the parameters.

      3. In the Field Mapping section, configure mappings between source fields and destination fields.

      4. In the Channel Control section, configure the parameters.

      For more information, see Configure a batch synchronization task by using the codeless UI.

    6. Run the task.

      1. (Optional) Configure scheduling properties for the task. In the right-side navigation pane, click Properties. On the Properties tab, configure the parameters based on your business requirements. For more information about the parameters, see Scheduling configuration.

      2. In the upper-left corner, click the Save icon to save the task.

      3. In the upper-left corner, click the Submit icon to submit the task.

        If you configure scheduling properties for the task, the task is automatically run on a regular basis. You can also click the Run icon in the upper-left corner to run the task immediately.

        If Shell run successfully! is displayed in operational logs, the task runs successfully.

    Step 4: Verify the data synchronization result

    1. Log on to the Kibana console of the Elasticsearch cluster.

      For more information, see Log on to the Kibana console.

    2. In the left-side navigation pane, click Dev Tools.

    3. On the Console tab, run the following command to view the synchronized data: 

      POST /hive_esdoc_good_sale/_search?pretty
{
"query": { "match_all": {}}
}
      Note

      Change hive_esdoc_good_sale to the value that you specified for the Index parameter when you configure the synchronization task.

      If the data is synchronized, the result shown in the following figure is returned.查看已经同步的数据