Add general mechanism for invalidating ongoing ops after a drop

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Incomplete
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.8.0-rc3
    • Component/s: Internal Code
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, anything using the creates a cursor can check if the cursor gets invalidated to determine if a drop occurred. We should also have something similar for other ops that doesn't need a cursor (for example, the Cloner).

            Assignee:
            Randolph Tan
            Reporter:
            Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: