[SERVER-50478] Consider separating OplogScan from CollectionScan Created: 22/Aug/20 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Bernard Gorman | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | qexec-team | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Execution
|
| Participants: |
| Description |
|
There is now quite a lot of oplog-specific functionality in the CollectionScan class (minTs/maxTs, timestamp tracking, etc). We should consider creating a dedicated OplogScan class to factor out this code and return CollectionScan to a more generic state. |