A change event’s value schema is the same in every change event that the connector generates for a particular table. The value’s schema, which describes the structure of the value’s payload. Descriptions of create event value fields Item "query": "INSERT INTO customers (first_name, last_name, email) VALUES ('Anne', 'Kretchmar', Table 8. It has the structure described by the previous schema field and it contains the actual data for the row that was changed. The second payload field is part of the event value. Typically, this schema contains nested schemas. In other words, the second schema describes the structure of the row that was changed. It specifies the Kafka Connect schema that describes what is in the event value’s payload portion.
The second schema field is part of the event value. It has the structure described by the previous schema field and it contains the key for the row that was changed. The first payload field is part of the event key. In this case, the first schema field describes the structure of the key identified by that property. It is possible to override the table’s primary key by setting the connector configuration property. In other words, the first schema field describes the structure of the primary key, or the unique key if the table does not have a primary key, for the table that was changed. It specifies a Kafka Connect schema that describes what is in the event key’s payload portion. The first schema field is part of the event key. Overview of change event basic content Item 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. 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": "CREATE TABLE products ( id INTEGER NOT NULL AUTO_INCREMENT PRIMARY KEY, name VARCHAR(255) NOT NULL, description VARCHAR(512), weight FLOAT ) ALTER TABLE products AUTO_INCREMENT = 101 ", "ddl": "ALTER TABLE customers ADD COLUMN middle_name VARCHAR(2000)", //