Static mappings - connect_cdc_sqdata

Static Mappings are the most common type and are explicitly specified in the Replicator script. The meaning and implication of the mapping items depend on the nature of the source and target. One MAPPINGS statement with multiple SOURCE entries will generally exist for each source Table or IMS DBD:

Syntax

MAPPINGS
SOURCE <table_name_1> | <dbd_name_1>
        [TOPIC <topic_name_1>]
        [SUBJECT <subject_1>]
        [ALIAS <alias_1>]
        [NAMESPACE <name_space_1>]
        [ROOTKEYLEN <key_length_1>]

[,SOURCE <table_name_2>  | <dbd_name_2
        TOPIC <topic_name_2>
        SUBJECT <subject_2>
        ALIAS <alias_2>
        NAMESPACE <name_space_2>] [, ...]
        ROOTKEYLEN <key_length_2>
;

Example 1

Two HR tables are captured, their AVRO schemas are managed by Confluent and both will be written to the same Kafka Topic.

MAPPINGS
   SOURCE 'IVP_HR.EMPLOYEE'
          TOPIC 'HR'
          SUBJECT 'SQDATA_DB2_HR_EMPLOYEE'
          ALIAS 'EMP'
  ,SOURCE 'IVP_HR.DEPARTMENT'
          TOPIC 'HR'
          SUBJECT 'SQDATA_DB2_HR_DEPARTMENT'
          ALIAS 'DEPT'
;

Example 2

Two IMS DBD's are captured and will be Distributed to two sets of Parallel Apply Engine Kafka Consumers. The root key length of the first DBD will be overridden to limit the number of parallel Apply Engines.

MAPPINGS
  SOURCE 'IVPHRDBD'
          SUBJECT '<HRDBD-value>
          ALIAS 'IVPHRCDC' ROOTKEYLEN <key_length_1>
		  
  ,SOURCE 'IVPDPDBD'
          SUBJECT '<DPDBD-value>
          ALIAS 'IVPDPCDC'

Note:

Avro Container targets use a file rotation method controlled by a size and or a delay. For hadoop (HDFS), if an OPTIONS statement does not define a size and delay, by default a delay of 1 hour is applied. A delay of one hour means that from the time a record is first written to a target file, the file will be rotated after one hour has passed, if the file has not been rotated for other reason.
As previously described, if Static MAPPINGS have been provided but one or more SOURCE <object names> have not been specified the default behavior of the Replicator will enable continuous operation when a new source objects is encountered for the first time and where the Replicator script has not been revised to provide for non-default options, i.e: Topic Names, AVRO Confluent Subjects, Aliases, etc. This default behavior can be prevented by including a MAPPINGS Exit (see Dynamic Mappings below) where the exit merely terminates execution of the Replicator.

Static mappings - connect_cdc_sqdata - Latest

Connect CDC (SQData) Replicator Engine