Parameters | Description |
Data Source | Available Greenplum Data Source. |
Database | Supports selecting or manually entering the database name to be read 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. |
Schema | Supports selection or manual input of the Schema name to be read. |
Table | Supports selecting or manually entering the table name to be read. |
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) | In actual business scenarios, it is common to synchronize data of the current day, with the where condition specified as gmt_create>$bizdate. The where condition can effectively perform incremental business synchronization. If the WHERE clause is not provided, including missing the key or value, the data synchronization is treated as full data synchronization. |
Parameters | Description |
Data Destination | Greenplum Data Source to be Written. |
Database | Supports selection or manual input of the database name to write to 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. |
Schema | Supports selection or manual input of the Schema name to be read. |
Table | Supports selection or manual input of the table name to write to If the data source network is not connected and the 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 | Before writing to this Greenplum Data Table, you can manually choose whether to clear the table. |
Batch Submission Size | The size of records for one-time batch submission can significantly reduce the number of network interactions between the data synchronization system and Greenplum and improve overall throughput. If the value is set too high, it may cause the data synchronization process to run into OOM exceptions. |
Pre-Executed SQL (Optional) | The SQL statement executed before the synchronization task. Fill in the correct SQL syntax according to the data source type, such as clearing the old data in the table before execution (truncate table tablename). |
Post-Executed SQL (Optional) | The SQL statement executed after the synchronization task. Fill in the correct SQL syntax according to the data source type, such as adding a timestamp (alter table tablename add colname timestamp DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP). |
Greenplum Data Type | Internal Types |
smallint,integer,bigint | Long |
decimal,double precision,real | Double |
character,character varying, | String |
date | Date |
boolean,bit | Boolean |
Internal Types | Greenplum Data Type |
Long | smallint,integer,bigint |
Double | decimal,double precision,real |
String | character,character varying |
Date | date |
Boolean | bit,boolean |
Was this page helpful?