Thread-through CollectionPtr into the onDelete OpObserver

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Execution Team 2022-11-14, Sharding EMEA 2022-10-03, Sharding EMEA 2022-10-17, Sharding EMEA 2022-10-31
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      With the CollectionPtr becoming the "interface" to all the snapshotted state of the services associated with a collection (namely Sharing and StorageExecution), we require access to the CollectionPtr in the OpObservers.

      This is the catch-all ticket to perform the code modifications in order to remove the tight coupling between Collection* and the OpObservers on the onDelete code path.

            Assignee:
            Daniel Gomez Ferro
            Reporter:
            Jordi Serra Torrens
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: