Move all unrelated work out of OpObserverImpl into a miscellaneous FallbackOpObserver

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Minor Change
    • Execution Team 2023-05-15
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      OpObserverImpl has far too many dependencies that are unnecessary.

      There are many code snippets that have bloated this entity that should be mechanically separated out and put into other OpObserver(s). For the purposes of this ticket and breaking the immediate dependency on OpObserverImpl, I will move all this code into a catch-all OpObserver. A future author could consider breaking these up into more logical blocks.

      Primarily, OpObserverImpl should have no need to communicate with these entities:

      • Scope
      • MongoDSessionCatalog
      • ReadWriteConcernDefaults
      • LogicalTimeValidator?

            Assignee:
            Matt Kneiser
            Reporter:
            Matt Kneiser
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: