tencent cloud

Tencent Cloud WeData

Release Notes
Dynamic Release Record (2026)
Product Introduction
Product Overview
Product Advantages
Product Architecture
Product Features
Application Scenarios
Purchase Guide
Billing Overview
Product Version Purchase Instructions
Execute Resource Purchase Description
Billing Modes
Overdue Policy
Refund
Preparations
Overview of Account and Permission Management
Add allowlist /security groups (Optional)
Sign in to WeData with Microsoft Entra ID (Azure AD) Single Sign-On (SSO)
Operation Guide
Console Operation
Project Management
Data Integration
Studio
Data Development
Data Analysis
Data Science
Data Governance (with Unity Semantics)
API Documentation
History
Introduction
API Category
Making API Requests
Smart Ops Related Interfaces
Project Management APIs
Resource Group APIs
Data Development APIs
Data Asset - Data Dictionary APIs
Data Development APIs
Ops Center APIs
Data Operations Related Interfaces
Data Exploration APIs
Asset APIs
Metadata Related Interfaces
Task Operations APIs
Data Security APIs
Instance Operation and Maintenance Related Interfaces
Data Map and Data Dictionary APIs
Data Quality Related Interfaces
DataInLong APIs
Platform Management APIs
Data Source Management APIs
Data Quality APIs
Platform Management APIs
Asset Data APIs
Data Source Management APIs
Data Types
Error Codes
WeData API 2025-08-06
Service Level Agreements
Related Agreement
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary

Impala Data Source

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2024-11-01 17:52:37

Supported Editions

Supported by Impala version 4.1.0.

Impala Offline Single Table Read Node Configuration




Parameters
Description
Data Source
Select the configured Impala data source from the source end.
Database
Supports selection or manual input of the library name to read from.
By default, the database bound to the data source is used as the default database. Other databases need to be manually entered.
If the data source network is not connected and the database information cannot be fetched directly, you can manually enter the database name. Data synchronization can still be performed when the Data Integration network is connected.
Table
Supports selecting or manually entering the table name to be read.
If the data source network is not connected and table information cannot be fetched directly, you can manually enter the table name. Data synchronization can still be performed when the Data Integration network is connected.
Split Key
Specify the field for data sharding. After specifying, concurrent tasks will be launched for data synchronization. You can use a column in the source data table as the partition key. It is recommended to use the primary key or indexed column as the partition key.
Filter Conditions (Optional)
Fill in the corresponding filter statement based on the data type. This statement will serve as the filter condition for the data to be synchronized.

Impala Offline Single Table Write Node Configuration




Parameters
Description
Data Destination
Select the configured Impala data source from the target end.
Database
Supports selection or manual input of the library name to read from.
By default, the database bound to the data source is used as the default database. Other databases need to be manually entered.
If the data source network is not connected and the database information cannot be fetched directly, you can manually enter the database name. Data synchronization can still be performed when the Data Integration network is connected.
Table
Supports selecting or manually entering the table name to be read.
If the data source network is not connected and table information cannot be fetched directly, you can manually enter the table name. Data synchronization can still be performed when the Data Integration network is connected.
Whether to Clear Table
You can manually choose whether to clear the Impala data table before writing to it.
Batch Submission Size
The size of the record batch submitted at once can greatly reduce the number of network interactions between the data synchronization system and Impala, enhancing overall throughput. If this value is set too high, it may cause the data synchronization process to encounter OOM exceptions.
Pre-Executed SQL
SQL statements executed before the synchronization task. Fill in the SQL according to the correct SQL syntax corresponding to the data source type.
Post-Executed SQL
SQL statements executed after the synchronization task. Fill in the SQL according to the correct SQL syntax corresponding to the data source type.

Data type conversion support

Read

Impala Data Type
Internal Types
BIGINT,INT,SMALLINT,TINYINT
Long
DECIMAL,DOUBLE,FLOAT,REAL
Double
CHAR,VARCHAR,ARRAY,STRUCT
String
TIMESTAMP
Date
BOOLEAN
Boolean

Write

Internal Types
Impala Data Type
Long
BIGINT,INT,SMALLINT,TINYINT
Double
DECIMAL,DOUBLE,FLOAT,REAL
String
CHAR,VARCHAR,ARRAY,STRUCT
Date
TIMESTAMP
Boolean
BOOLEAN

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan