[SERVER-68258] Refactor the logic to validate the collation parameter of shardCollection() Created: 25/Jul/22 Updated: 23/Jan/23 Resolved: 23/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Paolo Polato | Assignee: | Paolo Polato |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Sharding EMEA 2022-08-22, Sharding EMEA 2022-10-17, Sharding EMEA 2022-10-31, Sharding EMEA 2022-11-14, Sharding EMEA 2022-11-28, Sharding EMEA 2022-12-12, Sharding EMEA 2022-12-26, Sharding EMEA 2023-01-09, Sharding EMEA 2023-01-23 |
| Participants: |
| Description |
|
CreateCollectionCoordinator (the entity orchestrating the execution of a user db.shardCollectionRequest()) is defining a function to process the collation option of a request: the validation and application rules are not trivial and they cannot be easily deduced from the existing logic. This ticket aims to refactor the current code to make such rules explicit. |
| Comments |
| Comment by Paolo Polato [ 23/Jan/23 ] |
|
Closing this ticket - concerns about the correctness of the refactored code have been raised during the PR and the team is currently dedicating its bandwidth to higher-priority tickets. |