[SERVER-63663] Rename the DurableViewCatalog to something that does not suggest kinship to the DurableCatalog... Created: 15/Feb/22 Updated: 27/Oct/23 Resolved: 07/Oct/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | catalog, read-only-views | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
The name DurableViewCatalog makes me think that the class handles durability somehow: something low level like the DurableCatalog class. However, it doesn't at all. The DurableViewCatalog appears to just be a helper wrapper around accessing and modifying view Collections in the CollectionCatalog: a bit of abstraction for the fact that view modification is done via document writes instead of Collection metadata changes. Please name it something else.... |
| Comments |
| Comment by Gregory Noma [ 07/Oct/22 ] |
|
As of |
| Comment by Dianna Hohensee (Inactive) [ 04/Mar/22 ] |
|
The DurableViewCatalog appears to just be a helper wrapper around accessing and modifying view Collections in the CollectionCatalog. So, it shouldn't be pushed behind the CollectionCatalog, but perhaps it should be renamed..... Updated the ticket title & description. |