[SERVER-62687] Reject expireAfterSeconds with clusteredIndex when it's set to false Created: 17/Jan/22 Updated: 29/Oct/23 Resolved: 18/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jordi Olivares Provencio | Assignee: | Jordi Olivares Provencio |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Execution Team 2022-01-24 |
| Participants: |
| Description |
|
As discovered during a PR, creating a collection with {clusteredIndex: false, expireAfterSeconds: <num>} leads to a valid command execution. This means we are accepting options that aren't used as we are saying not to use clustering but at the same time giving clustering options, which gives the impression that everything was accepted when it was not. |
| Comments |
| Comment by Githook User [ 18/Jan/22 ] |
|
Author: {'name': 'Jordi Olivares Provencio', 'email': 'jordi.olivares-provencio@mongodb.com', 'username': 'jordiolivares'}Message: |