This topic describes the data types and parameters that are supported by AnalyticDB for MySQL 3.0 Reader and how to configure AnalyticDB for MySQL 3.0 Reader by using the codeless user interface (UI) and code editor.

AnalyticDB for MySQL 3.0 Reader reads data from tables stored in AnalyticDB for MySQL 3.0 databases. AnalyticDB for MySQL 3.0 Reader connects to a remote AnalyticDB for MySQL 3.0 database by using Java Database Connectivity (JDBC) and executes a SELECT statement to read data from the AnalyticDB for MySQL 3.0 database.

Data types

The following table lists the data types that are supported by AnalyticDB for MySQL 3.0 Reader.

Category AnalyticDB for MySQL 3.0 data type
Integer INT, INTEGER, TINYINT, SMALLINT, and BIGINT
Floating point FLOAT, DOUBLE, and DECIMAL
String VARCHAR
Date and time DATE, DATETIME, TIMESTAMP, and TIME
Boolean BOOLEAN

Parameters

Parameter Description Required Default value
datasource The name of the data source. It must be the same as the name of the added data source. You can add data sources by using the code editor. Yes No default value
table The name of the table from which you want to read data. Yes No default value
column The names of the columns from which you want to read data. The columns are specified in a JSON array. The default value is [*], which indicates all columns.
  • You can select specific columns to read.
  • The column order can be changed. You can read data from the specified columns in an order different from that specified in the schema of the table.
  • Constants are supported. The column names must be arranged in compliance with the SQL syntax supported by MySQL, such as ["id", "`table`", "1", "'bazhen.csy'", "null", "to_char(a + 1)", "2.3" , "true"].
    • id: a column name.
    • table: the name of a column that contains reserved keywords.
    • 1: an integer constant.
    • bazhen.csy: a string constant.
    • null: a null pointer.
    • to_char(a + 1): a function expression that is used to calculate the length of a string.
    • 2.3: a floating-point constant.
    • true: a Boolean value.
  • The column parameter must explicitly specify all the columns from which you want to read data. This parameter cannot be left empty.
Yes No default value
splitPk The field that is used for data sharding when AnalyticDB for MySQL 3.0 Reader reads data. If you specify this parameter, the source table is sharded based on the value of this parameter. Data Integration then runs parallel threads to read data. This way, data can be synchronized more efficiently.
  • We recommend that you set the splitPk parameter to the name of the primary key column of the table. Data can be evenly distributed to different shards based on the primary key column, instead of being intensively distributed only to specific shards.
  • The splitPk parameter supports sharding for data only of integer data types. If you set this parameter to a field of an unsupported data type, such as a string, floating point, or date data type, AnalyticDB for MySQL 3.0 Reader ignores the splitPk parameter and uses a single thread to read data.
  • If the splitPk parameter is not provided or is left empty, AnalyticDB for MySQL 3.0 Reader uses a single thread to read data.
No No default value
where The WHERE clause. For example, you can set this parameter to gmt_create > $bizdate to read data on the current day.
  • You can use the WHERE clause to read incremental data. If the where parameter is not provided or is left empty, AnalyticDB for MySQL 3.0 Reader reads all data.
  • Do not set the where parameter to limit 10, which does not conform to the constraints of MySQL on the SQL WHERE clause.
No No default value

Configure AnalyticDB for MySQL 3.0 Reader by using the codeless UI

  1. Configure data sources.
    Configure Source and Target for the synchronization node. Connections section
    Parameter Description
    Connection The name of the data source from which you want to read data. This parameter is equivalent to the datasource parameter that is described in the preceding section.
    Table The name of the table from which you want to read data. This parameter is equivalent to the table parameter that is described in the preceding section.
    Filter The condition used to filter the data that you want to read. Filtering based on the LIMIT keyword is not supported. The SQL syntax is determined based on the selected data source.
    Shard Key The shard key. You can use a column in the source table as the shard key. We recommend that you use the primary key column or an indexed column. Only integer columns are supported.
    If you specify this parameter, data sharding is performed based on the value of this parameter, and parallel threads can be used to read data. This improves data synchronization efficiency.
    Note The Shard Key parameter is displayed only after you select the data source for the synchronization node.
  2. Configure field mappings. This operation is equivalent to setting the column parameter that is described in the preceding section.
    Fields in the source on the left have a one-to-one mapping with fields in the destination on the right. You can click Add to add a field. To remove an added field, move the pointer over the field and click the Remove icon.
    Operation Description
    Map Fields with the Same Name Click Map Fields with the Same Name to establish mappings between fields with the same name. The data types of the fields must match.
    Map Fields in the Same Line Click Map Fields in the Same Line to establish mappings between fields in the same row. The data types of the fields must match.
    Delete All Mappings Click Delete All Mappings to remove the mappings that are established.
    Auto Layout Click Auto Layout. Then, the system automatically sorts the fields based on specific rules.
    Change Fields Click the Change Fields icon. In the Change Fields dialog box, you can manually edit the fields in the source table. Each field occupies a row. The first and the last blank rows are included, whereas other blank rows are ignored.
    Add
    • You can enter constants. Each constant must be enclosed in single quotation marks ('), such as 'abc' and '123'.
    • You can use scheduling parameters such as ${bizdate}.
    • You can enter functions that are supported by relational databases, for example, now() and count(1).
    • If the field that you entered cannot be parsed, the value of Type for the field is Unidentified.
  3. Configure channel control policies. Channel control
    Parameter Description
    Expected Maximum Concurrency The maximum number of parallel threads that the synchronization node uses to read data from the source or write data to the destination. You can configure the parallelism for the synchronization node on the codeless UI.
    Bandwidth Throttling Specifies whether to enable bandwidth throttling. You can enable bandwidth throttling and specify a maximum transmission rate to prevent heavy read workloads on the source. We recommend that you enable bandwidth throttling and set the maximum transmission rate to an appropriate value based on the configurations of the source.
    Dirty Data Records Allowed The maximum number of dirty data records allowed.
    Distributed Execution

    The distributed execution mode that allows you to split your node into pieces and distribute them to multiple Elastic Compute Service (ECS) instances for parallel execution. This speeds up synchronization. If you use a large number of parallel threads to run your synchronization node in distributed execution mode, excessive access requests are sent to the data sources. Therefore, before you use the distributed execution mode, you must evaluate the access load on the data sources. You can enable this mode only if you use an exclusive resource group for Data Integration. For more information about exclusive resource groups for Data Integration, see Exclusive resource groups for Data Integration and Create and use an exclusive resource group for Data Integration.

Configure AnalyticDB for MySQL 3.0 Reader by using the code editor

In the following code, a synchronization node is configured to read data from AnalyticDB for MySQL 3.0. For more information about the parameters, see the preceding parameter description.
{
    "type": "job",
    "steps": [
        { 
            "stepType": "analyticdb_for_mysql", // The reader type. 
            "parameter": {
                "column": [ // The names of the columns from which you want to read data. 
                    "id",
                    "value",
                    "table"
                ],
                "connection": [
                    {
                        "datasource": "xxx", // The name of the data source. 
                        "table": [ // The name of the table from which you want to read data. 
                            "xxx"
                        ]
                    }
                ],
                "where": "", // The condition used to filter data that you want to read. 
                "splitPk": "", // The shard key. 
                "encoding": "UTF-8" // The encoding format. 
            },
            "name": "Reader",
            "category": "reader"
        },
        { 
            "stepType": "stream",
            "parameter": {},
            "name": "Writer",
            "category": "writer"
        }
    ],
    "version": "2.0",
    "order": {
        "hops": [
            {
                "from": "Reader",
                "to": "Writer"
            }
        ]
    },
    "setting": {
        "errorLimit": {
            "record": "0" // The maximum number of dirty data records allowed. 
        },
        "speed": {
            "throttle":true,// Specifies whether to enable bandwidth throttling. The value false indicates that bandwidth throttling is disabled, and the value true indicates that bandwidth throttling is enabled. The mbps parameter takes effect only when the throttle parameter is set to true. 
                        "concurrent":1 // The maximum number of parallel threads. 
                      "mbps":"12"// The maximum transmission rate.
        }
    }
}