-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Labels:
-
Fully Compatible
-
v6.3, v6.0, v5.0
-
Execution Team 2023-03-20
When we print metadata for a record or index entry, we have the have the timestamp that last touched that value (stored in the startDurableTs variable). We would like to surface some additional information about the write, namely some data about the oplog entry associated with that timestamp, if the entry is still available.
If redaction works correctly with oplog entries, then we can likely just log the full entry; however, redaction generally expects a user document, not an oplog entry, so it may not work as expected. If that's the case, we should instead determine which information is safe to log, such as the entry type, and possibly the "shape" of the operation.
- causes
-
SERVER-80789 Make AutoGetOplog behave consistently in replica set node started as standalone
-
- Closed
-
- depends on
-
-
- Closed
-
-
-
- Closed
-
- related to
-
SERVER-80556 Log additional information about the oplog entry that generated a document or index key when printing metadata in dbCheck
-
- Backlog
-
-
-
- Backlog
-
-
-
- Closed
-