You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sql,log: add new txn_timestamp filed to CommonSqlEventDetails
Previously, an event's `timestamp` field was either set to
the current time, or the read timestamp of the txn emitting
the event, if the event was emitted within a txn. This isn't
obvious functionality and can result in events to be seemingly
out of order.
To fix this, we adeded a new `txn_timestamp` field to the
CommonSQLEventDetails proto type. This field is responsible
for holding the txn's current read timestamp that a structured
event was emitted in, if in a transaction. Now, an event's
timestamp will always be the time that the event was
constructred, and txn_timestamp will transactions current
read timestamp.
Resolves: #146820
Epic: None
Release note (general change): Updated SQL events to have a
'TxnTimestamp' which indicates the read timestamp of the
transaction that the sql event was emitted in, if in
a transaction. The `Timestamp` of an event will always be
the time that the event was created.
0 commit comments