[SERVER-17583] Add support for capped collection max in convertToCapped and cloneAsCapped Created: 13/Mar/15  Updated: 06/Dec/22  Resolved: 15/Apr/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Asya Kamsky Assignee: Backlog - Storage Execution Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Storage Execution
Participants:

 Description   

Tried in WT and MMAP to create capped collection: both fine.

Tried in both to convertToCapped, both ignored the max setting (converted to capped had capped:true and size:xxx correct, but for max mmap had "max" : NumberLong("9223372036854775807"), and WT had "max": -1



 Comments   
Comment by Eric Milkie [ 13/Mar/15 ]

Yes, neither convertToCapped nor cloneCollectionAsCapped commands support a non-default 'max' when creating the new capped collection.

Generated at Thu Feb 08 03:44:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.