[SERVER-52878] Separate oplog from regular collections Created: 16/Nov/20 Updated: 06/Dec/22 Resolved: 07/Dec/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Henrik Edin | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Duplicate | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
The amount of if (oplog) special handling is increasing. Collection copy-on-write is disabled for the oplog for example. When the oplog pretends to be just another collection it makes it difficult to understand its semantics. We should consider separating the oplog from regular collections. Let the oplog have its separate API when necessary to clarify the semantics and avoid conditionals in the implementation. |