* transaction, or false for when a connector resumes and takes a snapshot, * true if streaming should resume from the start of the snapshot * true if the snapshotter should stream after taking a snapshot * true if the snapshotter should take a snapshot Void init(PostgresConnectorConfig config, OffsetState sourceInfo, * Implementations must return true for either #shouldSnapshot()} or #shouldStream()} * can provide more advanced functionality, such as partial snapshots.
* a custom implementation of this interface can be provided by the implementor, which * While many default snapshot modes are provided with Debezium, * - What queries should be used to snapshot
* This interface is used to determine details about the snapshot process: If you do not specify a type value, the signal fails to stop the incremental snapshot. If this component of the data field is omitted, the signal stops the entire incremental snapshot that is in progress.Ī required component of the data field of a signal that specifies the kind of snapshot operation that is to be stopped.Ĭurrently, the only valid option is incremental. Specifies type parameter specifies the operation that the signal is intended to trigger.Īn optional component of the data field of a signal that specifies an array of table names or regular expressions to match table names to remove from the snapshot. Descriptions of fields in a SQL command for sending a stop incremental snapshot signal to the signaling table Item The following table describes the parameters in the example: Table 5. If you do not specify a value, the connector runs an incremental snapshot.įor more information about the additional-condition parameter, see Ad hoc incremental snapshots with additional-condition. The array lists regular expressions which match tables by their fully-qualified names, using the same format as you use to specify the name of the connector’s signaling table in the configuration property.Īn optional type component of the data field of a signal that specifies the kind of snapshot operation to run.Ĭurrently, the only valid option is the default value, incremental. The type parameter specifies the operation that the signal is intended to trigger.Ī required component of the data field of a signal that specifies an array of table names or regular expressions to match table names to include in the snapshot. Rather, during the snapshot, Debezium generates its own id string as a watermarking signal. Use this string to identify logging messages to entries in the signaling table.
The id parameter specifies an arbitrary string that is assigned as the id identifier for the signal request. Specifies the fully-qualified name of the signaling table on the source database. Descriptions of fields in a SQL command for sending an incremental snapshot signal to the signaling table Item The following table describes the parameters in the example: Table 3. The format of the names is the same as for the configuration option.Īn optional string, which specifies a condition based on the column(s) of the table(s), to capture aĪn optional string that specifies the column name that the connector uses as the primary key of a table during the snapshot process. Specifies the type of snapshot that you want to run.Ĭurrently, you can request only incremental snapshots.Īn array that contains regular expressions matching the fully-qualified names of the table to be snapshotted. Example of an ad hoc execute-snapshot signal record Field 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 2. You specify the tables to capture by sending an execute-snapshot message to the signaling table.
0 kommentar(er)
