Get rid of OperationContextNoop

XMLWordPrintableJSON

    • Sharding EMEA
    • Fully Compatible
    • Sharding EMEA 2023-06-12, Sharding EMEA 2023-06-26, Sharding EMEA 2023-07-10
    • 156
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The OperationContextNoop was introduced long time ago as means to abstract lock acquisitions and access to the recovery unit for unit-tests (and MongoS). With the unit-testing tools that we have now, such as ServiceContextTest, this seems to no longer be necessary, so we should try to get rid of it.

      The most usages seem to be in the Execution Team's test code, so I am assigning this ticket to their backlog.

            Assignee:
            Kaloian Manassiev
            Reporter:
            Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: