[SERVER-71313] Unify "hedged read" related-code naming in the server Created: 14/Nov/22 Updated: 30/Aug/23 Resolved: 30/Aug/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | George Wangensteen | Assignee: | Alex Li |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Service Arch
|
| Sprint: | Service Arch 2023-01-23, Service Arch 2023-02-06, Service Arch 2023-02-20, Service Arch 2023-03-06, Service Arch 2023-03-20, Service Arch 2023-04-03, Service Arch 2023-04-17, Service Arch 2023-05-01, Service Arch 2023-05-15, Service Arch 2023-05-29, Service Arch 2023-06-12, Service Arch 2023-06-26, Service Arch 2023-07-10, Service Arch 2023-08-07, Service Arch 2023-08-21, Service Arch 2023-09-04 |
| Participants: |
| Description |
|
Some of the server code pertaining to hedged reads lives in files whose names start with "hedge", while others live in files whose names start with "hedged". The same discrepancy applies for some of the types defined in those files. Let's unify the code base to use a single convention for code pertaining to this feature to make the code easier to search and navigate. |