[SERVER-61285] Capped parameter for the create command is currently stable Created: 05/Nov/21 Updated: 29/Oct/23 Resolved: 03/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Samyukta Lanka | Assignee: | Samyukta Lanka |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Replication 2021-11-15, Replication 2021-11-29, Replication 2021-12-13, Replication 2021-12-27, Replication 2022-01-10, Replication 2022-01-24, Replication 2022-02-07 |
| Participants: |
| Description |
|
Creating capped collections should not be a part of API V1. Other parameters that are required with capped were marked as unstable, so we don't think it's possible for anyone to make use of this behavior when apiStrict=true. Just to be sure, we need to verify that it is currently not possible to create a capped collection with apiStrict=true before we do this change. |
| Comments |
| Comment by Githook User [ 03/Feb/22 ] |
|
Author: {'name': 'Samy Lanka', 'email': 'samy.lanka@mongodb.com', 'username': 'lankas'}Message: |
| Comment by Samyukta Lanka [ 13/Jan/22 ] |
|
This work involves changing something that was previously stable to unstable, which has consequences for when the compatibility checker compares IDL between different versions. I don't think fixing this is worth the effort of making an exception in the compatibility checker, so I'm repurposing this ticket to add a test that it's not possible to create a capped collection with apiStrict=true. This ticket should also add a comment in the IDL to clarify that in practice the capped parameter is unstable. |