Set the type of the execute-snapshot signal to incremental, and provide the names of the tables to include in the snapshot, as described in the following table: Table 4. You specify the tables to capture by sending an execute-snapshot message to the signaling table. If MySQL applies them individually, the connector creates a separate schema change event for each statement.Īn array of one or more items that contain the schema changes generated by a DDL command.
If MySQL applies them atomically, the connector takes the DDL statements in order, groups them by database, and creates a schema change event for each group. Multiple DDL statements appear in the order in which they were applied to the database.Ĭlients can submit multiple DDL statements that apply to multiple databases. The ddl field can contain multiple DDL statements.Įach statement applies to the database in the databaseName field. This field contains the DDL that is responsible for the schema change. The value of the databaseName field is used as the message key for the record. Identifies the database and the schema that contains the change.
#MYSQL CREATE USER NETWORK MASK UPDATE#
By comparing the value for _ms with the value for payload.ts_ms, you can determine the lag between the source database update and Debezium. In the source object, ts_ms indicates the time that the change was made in the database. The time is based on the system clock in the JVM running the Kafka Connect task. Optional field that displays the time at which the connector processed the event. This field is useful to correlate events on different topics. The source field is structured exactly as standard data change events that the connector writes to table-specific topics. Descriptions of fields in messages emitted to the schema change topic Item "ddl": "ALTER TABLE customers ADD middle_name varchar(255) AFTER first_name", (4)
0 kommentar(er)
