[SERVER-67507] move OpObserver classes out of top-level mongo/db/ directory Created: 24/Jun/22 Updated: 29/Sep/22 Resolved: 08/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Shin Yee Tan |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Execution Team 2022-07-11, Execution Team 2022-07-25 | ||||||||
| Participants: | |||||||||
| Description |
|
The OpObserver interface and its implementations, including the OpObserverRegistry, currently reside in the top-level mongo/db directory of the source tree. We regularly extended the interface and add implementations (especially OpObserverImpl). It would help with maintenance if we consider providing a new subdirectory under mongo/db/ to hold these classes. |
| Comments |
| Comment by Githook User [ 08/Jul/22 ] |
|
Author: {'name': 'Shin Yee Tan', 'email': 'shinyee.tan@mongodb.com', 'username': 'shinyeet'}Message: |
| Comment by Githook User [ 08/Jul/22 ] |
|
Author: {'name': 'Shin Yee Tan', 'email': 'shinyee.tan@mongodb.com', 'username': 'shinyeet'}Message: |