DataWorks provides a one-click schema import feature to quickly create multiple Hologres external tables with schemas identical to those of your MaxCompute tables. This topic describes how to configure a one-click MaxCompute table schema synchronization node to import table schemas from MaxCompute into a Hologres database.
Background
DataWorks provides a visual interface that uses the IMPORT FOREIGN SCHEMA statement to quickly synchronize MaxCompute table schemas with Hologres.
Hologres is a one-stop real-time data warehouse engine developed by Alibaba Cloud. It seamlessly integrates with MaxCompute, so you can create external tables to accelerate queries on MaxCompute data.
Limitations
This feature only accelerates queries on MaxCompute internal tables. It does not support query acceleration for external tables or views.
Procedure
On the editor page for the one-click MaxCompute table schema synchronization node, complete the following steps.
Configure node information
On the node editor page, configure the following parameters:
Parameter
Description
Destination Name
The name of the Hologres instance.
NoteYou can click the destination management link to navigate to the Holo console (instance monitoring), Slow Query, Active connection management, DB authorization, or User management page.
Destination Database
The name of the database within the Hologres instance.
Schema
The name of the schema within the Hologres database. The default value is
public.Type
The source of the tables used to create the Hologres external tables. Currently, only MaxCompute is supported.
Servers
The server where the source tables are located.
You can directly use the odps_server external table server which is created by default in Hologres. For more information about the working principle, see postgres_fdw.
Source Project
The name of the project to which the source tables belong.
Select Tables For Query Acceleration
The source tables from which to create external tables.
All Tables in Database: Creates external tables for all tables in the selected project.
Selected Tables: Creates external tables for only the selected tables in the project. You can search for tables by name.
NoteThe search feature supports fuzzy matching. When you enter a keyword, all tables whose names contain the keyword are returned.
Action For Table Name Conflicts
Specifies how to handle a conflict if a table with the same name already exists in Hologres.
Ignore Conflicts and Continue Creating Tables
Update and Change Names of Tables with Same Names
Report Error and Create No Table
Data Type Not Supported
Specifies how to handle source data types that Hologres does not support.
Report Error and Import Failed: Fails the table creation.
Ignore and Skip Unsupported Fields: Skips the unsupported fields and continues to create the table.
Run the synchronization task
In the Run Configuration section, select a Resource Group.
NoteYou can also estimate the CUs required based on the resources that the task requires. The default value is
0.25.To access a data source over the Internet or a VPC, you must use a resource group for scheduling that can connect to the data source. For more information, see Network connectivity solutions.
On the toolbar, click Save to save the task, and then click Run to execute it.
To run the node on a schedule, configure its scheduling properties. For more information, see Scheduling configurations.
After you configure the node, you must commit and deploy it. For more information, see Node and workflow deployment.
After the task is deployed, you can view the status of scheduled tasks in Operation Center. For more information, see Get started with Operation Center.
Next steps
After the external tables are created, you must synchronize data into the corresponding Hologres tables. Then, use Hologres commands to accelerate queries on MaxCompute data. For more information, see Use a foreign table to accelerate queries on MaxCompute data.