Help Center/ DataArts Studio/ User Guide/ DataArts Migration (CDM Jobs)/ Creating a Job in a CDM Cluster/ Configuring CDM Source Job Parameters/ From REDSHIFT
Updated on 2026-03-20 GMT+08:00
View PDF
Share

From REDSHIFT

If the source link of a job is a REDSHIFT link, configure the source job parameters based on Table 1.

Currently, this data source supports only the DWS destination.

Table 1 Parameter description

Type

Parameter

Description

Example Value

Basic parameters

Use SQL Statement

Whether you can use SQL statements to export data from a relational database

No

SQL Statement

When Use SQL Statement is set to Yes, enter an SQL statement here. CDM exports data based on the SQL statement.

NOTE:
  • SQL statements can only be used to query data. Join and nesting are supported, but multiple query statements are not allowed, for example, select * from table a; select * from table b.
  • With statements are not supported.
  • Comments, such as -- and /*, are not supported.
  • Addition, deletion, and modification operations are not supported, including but not limited to the following:
    • load data
    • delete from
    • alter table
    • create table
    • drop table
    • into outfile
  • If the SQL statement is too long, the request fails to be delivered. If you continue to create a job, the system displays an error message indicating that the request is incorrect. In this case, you need to simplify or clear the SQL statement and try again.

select id,name from sqoop.user;

Schema/Tablespace

Name of the schema or tablespace from which data will be extracted. This parameter is displayed when Use SQL Statement is set to No. Click the icon next to the text box to go to the page for selecting a schema or directly enter a schema or tablespace.

If the desired schema or tablespace is not displayed, check whether the login account has the permissions required to query metadata.

NOTE:
The parameter value can contain wildcard characters (*), which is used to export all databases whose names start with a certain prefix or end with a certain suffix. The following are examples:
  • SCHEMA* indicates that all databases whose names starting with SCHEMA are exported.
  • *SCHEMA indicates that all databases whose names ending with SCHEMA are exported.
  • *SCHEMA* indicates that all databases whose names containing SCHEMA are exported.

SCHEMA_EXAMPLE

Table Name

Name of the table from which data will be extracted. This parameter is displayed when Use SQL Statement is set to No. Click the icon next to the text box to go to the page for selecting the table or directly enter a table name.

If the desired table is not displayed, check whether the table exists or whether the login account has the permission to query metadata.

This parameter can be configured as a macro variable of date and time and a path name can contain multiple macro variables. When the macro variable of date and time works with a scheduled job, the incremental data can be synchronized periodically. For details, see Incremental Synchronization Using the Macro Variables of Date and Time.

This parameter can be set to a regular expression to export all databases that meet the rule. For example, if Table Name is set to user_[0-9]{1,2}, tables from user_0 to user_9 and from user_00 to user_99 are matched.

NOTE:

If you have configured a macro variable of date and time and schedule a CDM job through DataArts Studio DataArts Factory, the system replaces the macro variable of date and time with (Planned start time of the data development job – Offset) rather than (Actual start time of the CDM job – Offset).

TABLE_EXAMPLE

Advanced attributes

WHERE Clause

WHERE clause used to specify the data extraction range. This parameter is displayed when Use SQL Statement is set to No. If this parameter is not set, the entire table is extracted.

You can set a date macro variable to extract data generated on a specific date. For details, see Incremental Migration of Relational Databases.

NOTE:

If you have configured a macro variable of date and time and schedule a CDM job through DataArts Studio DataArts Factory, the system replaces the macro variable of date and time with (Planned start time of the data development job – Offset) rather than (Actual start time of the CDM job – Offset).

DS='${dateformat(yyyy-MM-dd,-1,DAY)}'

Retain One Decimal Place for Date Values

Whether to retain one decimal place for date values

false

Split Job

Whether to split a job into subjobs based on a field value.

Yes

Job Split Field

This parameter is displayed when Split Job is set to Yes.

The job split field can be of the integer or FLOAT type.

-

Minimum Split Field Value

This parameter is displayed when Split Job is set to Yes.

It indicates the minimum value of the split field. The value must be less than or equal to the minimum value of the split field of the source job. Otherwise, data will be lost during the migration.

-

Maximum Split Field Value

This parameter is displayed when Split Job is set to Yes.

It indicates the maximum value of the split field. The value must be greater than or equal to the maximum value of the split field of the source job. Otherwise, data will be lost during the migration.

-

Subjobs

This parameter is displayed when Split Job is set to Yes.

It indicates the number of subjobs into which a job is split based on the field.

-