Allow registering multiple OpObservers, axe OpObserverNoop

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.7.1
    • Affects Version/s: None
    • Component/s: Replication, Storage
    • Fully Compatible
    • Storage 2017-06-19, Storage 2017-07-10, Storage 2017-07-31, Storage 2017-12-18, Storage 2018-01-01
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      With the collection UUID project it has become clear that for testing we might want some OpObservers and not others. Additionally, having a single OpObserverImpl requires largely unrelated code to all live in the same place, which is not ideal for clarity and maintenance.

      So, create a OpObserverRegistry that can register observers that will be called in sequence.

            Assignee:
            Geert Bosch
            Reporter:
            Geert Bosch
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: