Remove dependency of `catalog_impl` on `oplog`

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Sharding EMEA 2022-07-25, Sharding EMEA 2022-08-08
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, there is a circular dependency between the `oplog` library and `catalog_impl`, which links just because the Collection class is virtual. With CRUD (or rather any writing code) being pulled out of CollectionImpl, this class will become the lowest possible denominator for operations against the catalog and it will be below the `oplog` hierarchically.

      Temporarily they will have to interact through the `LocalOpLog` interface and this ticket is to perform this decoupling.

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

                Created:
                Updated:
                Resolved: