true
. Write messages to separate table-specific topics.
false
. Write all messages to the single topic that has the name specified in the topicName field.

softDeletes. Apply source delete operations to the target as soft deletes. A soft delete marks the deleted row as deleted without actually removing it from the database. For example, a delete on the source results in a change record on the target with "D" displayed in the INFA_OPERATION_TYPE column.
After enabling Soft Deletes, any update in the source table during normal or backlog mode results in the deletion of the matching record, insertion of the updated record, and marking of the INFA_OPERATION_TYPE operation as NULL in the target table. Similarly, inserting a record in the source table during backlog mode results in marking the INFA_OPERATION_TYPE operation as E in the target table record.
Consider using soft deletes if you have a long-running business process that needs the soft-deleted data to finish processing, to restore data after an accidental delete operation, or to track deleted values for audit purposes.
audit. Apply an audit trail of every DML operation made on the source tables to the target. A row for each DML change on a source table is written to the generated target table along with the audit columns you select. The audit columns contain metadata about the change, such as the DML operation type, time, owner, transaction ID, generated ascending sequence number, and before image. Consider using the Audit apply mode when you want to use the audit history to perform downstream computations or processing on the data before writing it to the target database or when you want to examine metadata about the captured changes.
If you use
Query-based
CDC method, this property is not applicable.
Standard. If you do not specify the auditData property, the task applies standard by default. In standard mode, the task accumulates the changes in a single apply cycle and intelligently merge them into fewer SQL statements before applying them to the target. For example, if an update followed by a delete occurs on the source row, no row is applied to the target. If multiple updates occur on the same column or field, only the last update is applied to the target. If multiple updates occur on different columns or fields, the updates are merged into a single update record before being applied to the target.

AVRO
CSV
PARQUET

true
. Write data in uncompressed Parquet format.
false
. Write data in AVRO format.

Binary
JSON

true
. Use the source table or object names as the names of the directories for each job run.
false
. Create a new set of directories for each job run by using the following naming pattern: tablename_timestamp.

Deflate
gzip
Snappy

None
Bzip2
Deflate
Snappy

None
gzip
Snappy

true
. Add the "dt=" prefix to the names of apply cycle directories.
false
. Do not change the names of apply cycle directories.

 - source: "*"
      target: "*_1"

true
. Use asynchronous delivery. Data Ingestion and Replication sends messages as soon as possible, without regard for the order in which the changes were retrieved from the source.
false
. Use synchronous delivery. Kafka must acknowledge each message as received before Data Ingestion and Replication sends the next message. In this mode, Kafka is unlikely to receive duplicate messages. However, performance might be slower.

Same as source
. Use the same case as the source table (or object) names and column (or field) names. Enter value "none" to use this option.
UPPERCASE
. Use all uppercase.
lowercase
. Use all lowercase.

true. Create a timestamp subdirectory for each CDC cycle under the summary contents and completed subdirectories.
false. Write individual data files to the same directory without a timestamp, unless you define an alternative directory structure.

true. Create a timestamp subdirectory for each CDC cycle under the summary contents and completed subdirectories.
false. Do not create timestamp subdirectories under the summary contents and completed subdirectories.

true. List individual data files under the contents subdirectory.
false. Do not list individual data files under the contents subdirectory.