[SERVER-29602] Allow registering multiple OpObservers, axe OpObserverNoop Created: 13/Jun/17 Updated: 30/Oct/23 Resolved: 25/Dec/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Geert Bosch | Assignee: | Geert Bosch |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Storage 2017-06-19, Storage 2017-07-10, Storage 2017-07-31, Storage 2017-12-18, Storage 2018-01-01 |
| Participants: |
| Description |
|
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. |
| Comments |
| Comment by Githook User [ 22/Dec/17 ] |
|
Author: {'username': 'stbrody', 'name': 'Spencer T Brody', 'email': 'spencer@mongodb.com'}Message: |
| Comment by Githook User [ 21/Dec/17 ] |
|
Author: {'name': 'Geert Bosch', 'email': 'geert@mongodb.com', 'username': 'GeertBosch'}Message: Also removes sharding specific interfaces for OpObserver. |