debezium / debezium/dbz

Log additional in-flight transaction metadata

Open
#2,576 0 comments 0 reactions 1 assignee Claimed by @Naros View on GitHub
component/oracle-connector type/task
Dominant language
HTML
Stars
6
Forks
8
Avg merge
2d 19h
Merged PRs (30d)
1

Description

The current process for the LogMiner buffered implementation is to log entries like the following at DEBUG level if there are any cached transactions that haven't yet rolled back or committed.
```
XID1 (SCN), XID2 (SCN), ...
```
The `Transaction` manages other metadata such as creation time and number of events. It would be helpful for administrators to have this information so they can make a better-informed decision about dropping a transaction without having to rely on manual LogMiner queries.

In addition, when using the deferred transaction configuration, it would also be helpful to include the state of the deferred transaction map in this logged output. A deferred transaction carries similar information, so having a second log entry for deferred transactions would easily work with the same logged setup.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.