Consider separating OplogScan from CollectionScan

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Execution
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            [DO NOT USE] Backlog - Query Execution
            Reporter:
            Bernard Gorman
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: