Check for "user write blocking" on collection acquisition instead of on op_observer

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Currently create/update/delete op_observers check that user write blocking is not enabled for every single write. This can have a performance impact.
      A better architecture could be to check it at collection acquisition time, and on restore from yield.

            Assignee:
            [DO NOT USE] Backlog - Catalog and Routing
            Reporter:
            Jordi Serra Torrens
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: