When a timestamp column is added and Formatter.formatterAddedTimestampUseSource=true, the timestamp always defaults to current date and time.

If you set the Connector.checkpointsInTarget property to true, you cannot adjust the Connector.checkpointMessageFrequency and Connector.checkpointTimeFrequency settings to provide periodic backup of checkpoints unless you set the Connector.kafkaProducerGuaranteeDelivery property to false.

When storing checkpoints in Kafka message headers and while writing the checkpoint information to the file as determined by the Connector.checkpointMessageFrequency and the Connector.checkpointTimeFrequency settings, Publisher stops writing the checkpoint information when the end of log is reached and before the file-based checkpoint is in synch with message header.

When you apply custom pattern formatting to TIMESTAMP WITH TIME ZONE columns with dates of 1/1/0001, CDC Publisher might fail.

Do not reference excluded columns in uncommented Custom Pattern Formatter <DT_SWAP> or <DT_MASK> column attributes as the columns might be included in messages regardless of the <EXCLUDE> column attribute settings.

When the delimiter is set to the pipe character ("|") in the Custom Pattern Formatter, an extraneous delimiter appears at the end of the published messages and in the validation report.

INFA* default columns and values are not generated when the include_default_metadata_columns parameter is set to true in the Custom Pattern Formatter custom pattern data file.

The Custom Pattern Formatter <DT_MASK> tag does not support the use of the "Z" timezone format string.

On startup, CDC Publisher displays warning messages about multiple SLF4J bindings. To remove these messages, remove the pwx-cdcpublisherMonitor-1.5.0.jar file from the CDC Publisher /lib directory.

When set to true, the following avroUseLogicaltype properties are not compatible with the Custom Pattern Formatter:

PowerExchange CDC Publisher fails against Confluent Schema Registry version 5.5. CDC Publisher uses Avro version 1.8 and Confluent version 5.5 requires Avro version 1.9.

Workaround: CDC Publisher is successful against the Confluent version 5.5 server if CDC Publisher uses the Confluent 5.3.1 client jar files. Confluent version 5.3.1 client jar files are placed in the directory that is referenced by the KAFKA_CLIENT_LIBS environment variable instead of the Confluent version 5.5 jar files.

If you copy the PwxCDCPublLog4j.xml file from the config subdirectory of an existing CDC Publisher instance to the config subdirectory on another instance, CDC Publisher does not recognize the new instance as the destination for message logging. Instead, CDC Publisher continues to log messages to the instance from which the PwxCDCPublLog4j.xml file was copied.

Workaround: On the new destination instance, copy the PwxCDCPublLog4j.xml file from the samples subdirectory to the config subdirectory. CDC Publisher can then recognize the new instance as the destination for logging messages.