[SERVER-18934] Don't require storage engines to implement oplog visibility rules Created: 11/Jun/15  Updated: 18/Jan/24

Status: Backlog
Project: Core Server
Component/s: Internal Code, Storage
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Mathias Stearn Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by WT-8169 Proposal for restricting the timestam... Backlog
is depended on by SERVER-55476 Database profiling should not seriali... Closed
Related
is related to SERVER-84449 High load can cause replication lag l... Open
Assigned Teams:
Storage Execution
Sprint: Execution Team 2022-01-10, Execution Team 2022-01-24, Execution Team 2022-02-21
Participants:

 Description   

Currently doc-locking engines must support some complex rules to control what documents in a capped collection are "visible". We should move that responsibility above the storage engine layer, at least for capped collections.



 Comments   
Comment by Eric Milkie [ 15/Nov/16 ]

This actually only applies to the special oplog collection now, I believe.

Generated at Thu Feb 08 03:49:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.