[SERVER-60265] Disallow specific fields from clustered collection creation Created: 27/Sep/21 Updated: 29/Oct/23 Resolved: 13/Oct/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.2.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Haley Connelly | Assignee: | Josef Ahmad |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-2311-M1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Execution Team 2021-10-18 |
| Participants: | |
| Story Points: | 1 |
| Description |
|
One example is viewOn doesn't make sense when creating a clustered collection. Investigate which fields to allow with clustered collection creation and which conflict. Ensure the restrictions are enforced. |
| Comments |
| Comment by Githook User [ 13/Oct/21 ] |
|
Author: {'name': 'Josef Ahmad', 'email': 'josef.ahmad@mongodb.com', 'username': 'josefahmad'}Message: |
| Comment by Josef Ahmad [ 12/Oct/21 ] |
|
Thanks Haley. As this ticket validates collection creation, let's defer the createIndex validation you propose to its dedicated ticket |
| Comment by Haley Connelly [ 05/Oct/21 ] |
|
A test should be included that also confirms it is illegal to create an index identical to the clusterKey eg) assert.commandFailedWithCode(db[collName].createIndex({_id: 1}), ErrorCodes.IndexAlreadyExists); |