filters for each data collection.\n* The data-collection property is the fully-qualified name of the data collection that the filter applies to. For more information about the additional-conditions parameter, see Running an ad hoc incremental snapshots with additional-conditions.\n\nRunning an ad hoc incremental snapshots with additional-conditions\n\nIf you want a snapshot to include only a subset of the content in a table, you can modify the signal request by appending an additional-conditions parameter to the snapshot signal.\n\nThe SQL query for a typical snapshot takes the following form:\n\nSELECT * FROM ....\n\nBy adding an additional-conditions parameter, you append a WHERE condition to the SQL query, as in the following example:\n\nSELECT * FROM WHERE ....\n\nThe following example shows a SQL query to send an ad hoc incremental snapshot request with an additional condition to the signaling table:\n\nINSERT INTO (id, type, data) VALUES ('', '', '{\"data-collections\": [\"\",\"\"],\"type\":\"\",\"additional-conditions\":[{\"data-collection\": \"\", \"filter\": \"\"}]}');\n\nFor example, suppose you have a products table that contains the following columns:\n\nid (primary key)\n\ncolor\n\nquantity\n\nIf you want an incremental snapshot of the products table to include only the data items where color=blue, you can use the following SQL statement to trigger the snapshot:\n\nINSERT INTO db1.debezium_signal (id, type, data) VALUES('ad-hoc-1', 'execute-snapshot', '{\"data-collections\": [\"db1.products\"],\"type\":\"incremental\", \"additional-conditions\":[{\"data-collection\": \"db1.products\", \"filter\": \"color=blue\"}]}');\n\nThe additional-conditions parameter also enables you to pass conditions that are based on more than one column. For example, using the products table from the previous example, you can submit a query that triggers an incremental snapshot that includes the data of only those items for which color=blue and quantity>10:\n\nINSERT INTO db1.debezium_signal (id, type, data) VALUES('ad-hoc-1', 'execute-snapshot', '{\"data-collections\": [\"db1.products\"],\"type\":\"incremental\", \"additional-conditions\":[{\"data-collection\": \"db1.products\", \"filter\": \"color=blue AND quantity>10\"}]}');\n\nThe following example, shows the JSON for an incremental snapshot event that is captured by a connector.\n\nExample 1. Incremental snapshot event message\n{\n \"before\":null,\n \"after\": {\n \"pk\":\"1\",\n \"value\":\"New data\"\n },\n \"source\": {\n ...\n \"snapshot\":\"incremental\" \n },\n \"op\":\"r\", \n \"ts_ms\":\"1620393591654\",\n \"ts_us\":\"1620393591654547\",\n \"ts_ns\":\"1620393591654547920\",\n \"transaction\":null\n}\nTable 5. Description of fields in an incremental snapshot event message\nItem\tField name\tDescription\n\n\n1\n\n\t\n\nsnapshot\n\n\t\n\nSpecifies the type of snapshot operation to run.\nCurrently, the only valid options are blocking and incremental.\nSpecifying a type value in the SQL query that you submit to the signaling table is optional.\nIf you do not specify a value, the connector runs an incremental snapshot.\n\n\n\n\n2\n\n\t\n\nop\n\n\t\n\nSpecifies the event type.\nThe value for snapshot events is r, signifying a READ operation.\n\nUsing the Kafka signaling channel to trigger an incremental snapshot\n\nYou can send a message to the configured Kafka topic to request the connector to run an ad hoc incremental snapshot.\n\nThe key of the Kafka message must match the value of the topic.prefix connector configuration option.\n\nThe value of the message is a JSON object with type and data fields.\n\nThe signal type is execute-snapshot, and the data field must have the following fields:\n\nTable 6. Execute snapshot data fields\nField\tDefault\tValue\n\n\ntype\n\n\t\n\nincremental\n\n\t\n\nThe type of the snapshot to be executed. Currentl

Debezium connector for MySQL :: Debezium Documentation

Podcast Information

Roles

Scripts