[SERVER-33048] Add check to determine if idIndex request matches actual _id options in _configCreateCommand Created: 31/Jan/18 Updated: 14/Apr/23 Resolved: 14/Apr/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.7.1 |
| Fix Version/s: | 5.0.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Marcos José Grillo Ramirez |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | RachitaD, pm-1051-legacy-tickets, sharding-common-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||
| Sprint: | Sharding 2018-03-26, Sharding 2018-04-09, Sharding 2018-04-23, Sharding 2018-05-21, Sharding 2018-06-04, Sharding 2018-06-18, Sharding 2018-07-16, Sharding 2018-07-30, Sharding 2018-08-13, Sharding EMEA 2023-04-17 | ||||||||
| Participants: | |||||||||
| Description |
|
Currently, the resulting _id index generated from a create collection can have more options compared to the idIndex options specified in the command request. As a result, if an attempt was made to call create with idIndex on a collection that already exist, but with a different _id index, it will not cause an error. Additional logic will be needed to compare if both are semantically equivalent. |
| Comments |
| Comment by Marcos José Grillo Ramirez [ 14/Apr/23 ] |
|
When SERVER-54587 was committed, extra checks were added when creating the sharded collection to prevent other creation commands on the same namespace to start, and if two different index formats are specified as shard key (even if using _id as sharded key), a ConflictingOperationInProgress error will be thrown. |