[SERVER-56999] Unify CollectionImpl creation interface Created: 17/May/21 Updated: 29/Oct/23 Resolved: 15/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Henrik Edin | Assignee: | Malik Endsley (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | catalog, neweng, techdebt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Execution Team 2023-06-12, Execution NAMR Team 2023-06-26 | ||||||||
| Participants: | |||||||||
| Description |
|
There are two constructors to CollectionImpl, one taking the whole metadata object from the DurableCatalog and one for just the CollectionOptions. Ideally it would be a nicer encapsulation if the metadata was read when creating the CollectionImpl but it is often needed before the CollectionImpl instance is created. We should unify the interfaces and fix so all callsites creating collections can use the interface that provides the metadata. |
| Comments |
| Comment by Githook User [ 15/Jun/23 ] |
|
Author: {'name': 'Malik Endsley', 'email': 'malik.endsley@mongodb.com', 'username': 'malikendsley'}Message: |