[SERVER-54446] Accept "clusteredIndex" option for collection creation on timeseries bucket collections Created: 10/Feb/21 Updated: 29/Oct/23 Resolved: 04/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Louis Williams |
| 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 2021-03-08 |
| Participants: |
| Description |
|
We need to accept the currently rejected "clusteredIndex" parameter for collection creation, but only on timeseries bucket collections. This option is currently only used internally, but mongo tools use the output of listCollections to clone collections. Since "clusteredIndex" shows up in listCollections, we cannot reject the parameter. Test that the output of listCollections on a timeseries buckets collection can be used to create a new collection. |
| Comments |
| Comment by Githook User [ 04/Mar/21 ] |
|
Author: {'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}Message: |