百度智能云

All Product Document

          Database Transmission Server

          Palo as Destination

          1. Applicable Scenarios

          This document applies to scenarios where you migrate a DTS-supported data source to a Palo destination using the Baidu AI Cloud Data’s Transmission Service DTS.

          2 Restrictions on Using Palo Database as DTS destination

          • Structure migration isn’t supported

          3 Prerequisites for Palo Database as DTS destination

          3.1 Requirements for Privilege of Database Account

          destination:

          Database Total increment migration
          Palo database LOAD_PRIV: Import privilege of the designated database or table

          4 Application of Palo Database as DTS destination

          For the operation processes, including task creation, task configuration, pre-check, task start, task pause, and task termination during the use of a Palo database as the destination, see Best Practice Documentation. It is slightly different from other data sources in the task configuration parameters and object mapping parts.

          4.1 Task Configuration Parameters

          image.png

          As shown in the figure above. The instructions for configuration parameters at the Palo destination of DTS are as below:

          • Access Type: The Baidu AI Cloud supported Palo instance.
          • Data Type: The regularly selected Palo.
          • IP/Port: The access IP and service port of a Palo database.
          • HTTP Port: The data import port of a Palo database.
          • Database: The database name to be migrated in the Palo database.
          • Account: The Palo database account.
          • Password: The password corresponding to the database account.

          4.2 Object Mapping

          DTS provides a database table name mapping feature for you to choose. As shown in the following figure, the selected migration objects may appear in the list of the selected objects on the right side. DTS supports the upstream and downstream database table name mapping, the column filter of blacklist/whitelist, and other features. You can click “Edit” to configure the mapping and filtration rules for each migration object.

          After you finish the mapping configuration of the objects, click Save and Pre-check to start the Pre-check of the task.

          5 Palo destination Data Types Supported by DTS

          The following table lists the default mapping between the DTS data types supported by DTS and the Palo destination data types.

          For any information on how to view the data types mapped at the source end, see the Data Type Mapping of Source-end Data Sources.

          DTS Field Type Palo Data Type
          DTS_TYPE_BOOLEAN tinyint
          DTS_TYPE_INT1 tinyint
          DTS_TYPE_INT2 smallint
          DTS_TYPE_INT4 integer
          DTS_TYPE_INT8 bigint
          DTS_TYPE_FLOAT float
          DTS_TYPE_DOUBLE double
          DTS_TYPE_DATE date
          DTS_TYPE_TIME datetime
          DTS_TYPE_DATETIME datetime
          DTS_TYPE_STRING If the fixed byte length && is <=255 bytes, use CHAR; and if the byte length is<=65535 bytes, use VARCHAR.
          DTS_TYPE_NUMBER In case of the precision <=27 && the scale <=9, use DECIMAL (p,s); if not, use varchar(....)
          Previous
          PostgreSQL as Destination
          Next
          Elasticsearch as DTS Destination