tencent cloud

Feedback

OceanBase Data Source

Last updated: 2024-11-01 17:48:13
    Note:
    Please note that OceanBase data source requires allowlist usage.

    OceanBase Offline Single Table Read Node Configuration

    
    
    
    Parameters
    Description
    Data Source Mode
    Supports MySQL Compatibility Mode and Oracle Compatibility Mode
    Data Source
    Available OceanBase 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.
    Table
    Supports selecting or manually entering the table name to be read.
    Add Shared Database/Table
    Applicable to sharding scenarios. Click to configure multiple data sources, databases, and table information. In sharding scenarios, ensure all table structures are consistent. The task configuration will default to displaying and using the structure of the first table to obtain data.
    Split Key
    You can use a column from the source data table as a split key; it is recommended to use the primary key or an indexed column as the split key. Only fields of integer type are supported.
    When reading data, data sharding is performed based on the configured fields to achieve concurrent reading, improving data synchronization efficiency.
    Filter Conditions (Optional)
    Fill in the corresponding filter statement according to the data type. This statement will serve as the filter condition for the data to be synchronized. Limit keywords are not supported at present. SQL syntax aligns with the selected data source.

    OceanBase Offline Single Table Write Node Configuration

    
    
    
    Parameters
    Description
    Data Source Mode
    Supports MySQL Compatibility Mode and Oracle Compatibility Mode
    Data Destination
    Available OceanBase Data Source.
    Write Type
    (MySQL Compatibility Mode)
    Single table write: Supports single table writing
    Write to Sharded Database/Tables: Supports one-time writing into sharded MySQL tables within the same data source. Ensure all table schemas are consistent and all target tables exist.
    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.
    Table
    Supports selecting or manually entering the table name to be read.
    Whether to Clear Table
    Before writing to the MySQL data table, you can manually choose whether to clear the data table.
    Write Mode
    Three modes are supported for writing in MySQL Compatibility Mode:
    Append: When a primary key/unique index conflict occurs, the conflicting rows cannot be written.
    Overwrite: In case of primary key/unique index conflict, the original row will be deleted first, and then the new row will be inserted.
    On duplicate key: In case of primary key/unique index conflict, the new row will replace the specified fields in the statement.
    Two modes are supported for writing in Oracle Compatibility Mode:
    Append: Append write.
    Upsert: Updates data based on the set primary key fields.
    Batch Submission Size
    The number of records submitted in a single batch. This value can greatly reduce the number of network interactions between the data synchronization system and OceanBase, enhancing overall throughput. If this value is set too high, it may cause data synchronization process 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).
    Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support