DBZ-5170 Update transaction ts_ms field to related doc

This commit is contained in:
harveyyue 2022-06-09 00:44:51 +08:00 committed by Jiri Pechanec
parent 20dc353262
commit 68a78f73bb
4 changed files with 4 additions and 0 deletions

View File

@ -582,6 +582,7 @@ Transaction boundary events contain the following fields:
`status`:: `BEGIN` or `END`.
`id`:: String representation of the unique transaction identifier.
`ts_ms`:: The time of `BEGIN` or `END` transaction.
`event_count` (for `END` events):: Total number of events emitted by the transaction.
`data_collections` (for `END` events):: An array of pairs of `data_collection` and `event_count` elements.
that indicates the number of events that the connector emits for changes that originate from a data collection.

View File

@ -429,6 +429,7 @@ Transaction boundary events contain the following fields:
`status`:: `BEGIN` or `END`
`id`:: String representation of unique transaction identifier.
`ts_ms`:: The time of `BEGIN` or `END` transaction.
`event_count` (for `END` events):: Total number of events emmitted by the transaction.
`data_collections` (for `END` events):: An array of pairs of `data_collection` and `event_count` elements that indicates number of events that the connector emits for changes that originate from a data collection.

View File

@ -410,6 +410,7 @@ For every transaction `BEGIN` and `END`, {prodname} generates an event that cont
* `status` - `BEGIN` or `END`
* `id` - string representation of unique transaction identifier
* `ts_ms` - The time of `BEGIN` or `END` transaction.
* `event_count` (for `END` events) - total number of events emitted by the transaction
* `data_collections` (for `END` events) - an array of pairs of `data_collection` and `event_count` that provides the number of events emitted by changes originating from given data collection

View File

@ -97,6 +97,7 @@ Transaction boundary events contain the following fields:
`status`:: `BEGIN` or `END`.
`id`:: String representation of the unique transaction identifier.
`ts_ms`:: The time of `BEGIN` or `END` transaction.
`event_count` (for `END` events):: Total number of events emitted by the transaction.
`data_collections` (for `END` events):: An array of pairs of `data_collection` and `event_count` elements.
that indicates the number of events that the connector emits for changes that originate from a data collection.