[SERVER-76129] Break out Time-Series event handling into its own OpObserver Created: 14/Apr/23 Updated: 29/Oct/23 Resolved: 18/Apr/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Matt Kneiser | Assignee: | Matt Kneiser |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||
| Sprint: | Execution Team 2023-05-01 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
The BucketCatalog has its notifications tied up in OpObserverImpl, when there is nothing special necessitating this. To slim down OpObserverImpl and make dependencies clearer, Time-Series state management and event handling should be owned by its own OpObserver. |
| Comments |
| Comment by Githook User [ 18/Apr/23 ] |
|
Author: {'name': 'Matt Kneiser', 'email': 'matt.kneiser@mongodb.com', 'username': 'themattman'}Message: |