| Change type | Description |
|---|---|
| Updated in version 5.0.6 | Updated to include Protobuf schema generation alongside AVRO. |
While the Replicator Engine will receive source database schemas from the Capture/Publisher and automatically generate the required AVRO or Protobuf schemas, it is necessary to identify the source tables that will be processed by the Replicator Engine in its script.
Note: The Engines will automatically handle both Code page translation and Data Type transformation as well as provide for the handling of invalid source data when applicable.
Example
Unlike the Apply Engine example, the Replicator Engine script requires only the Source Table Names and specification of the Topic and Subject whose content will contain values defined by the planners and architects of the organization's Confluent Schema Registry. The examples used here are arbitrary but were selected based on the source Table Names, source application and schema source, in this example, the EMPLOYEE and DEPARTMENT Tables, a Db2 "IVP_HR" Database and SQData respectively.
MAPPINGS
SOURCE 'IVP_HR.EMPLOYEE'
TOPIC IVP_HR_EMPLOYEE
SUBJECT IVP_HR_EMPLOYEE-value;
ALIAS 'EMPLOYEE'
,SOURCE 'IVP_HR.DEPARTMENT'
TOPIC IVP_HR_DEPARTMENT
SUBJECT IVP_HR_DEPARTMENT-value;
ALIAS 'DEPARTMENT';