[DOCS-557] Add note on convertToCapped behaviour when collection has data greater than the new capped collection size Created: 26/Sep/12  Updated: 30/Oct/23  Resolved: 04/Oct/12

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: Stennie Steneker (Inactive) Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 11 years, 19 weeks, 5 days ago

 Description   

Add a note to: http://docs.mongodb.org/manual/reference/command/convertToCapped/

The original collection will be followed in $natural order and loaded into a new capped collection. If you choose a smaller size (in bytes) for the capped collection than the current uncapped collection, documents will be aged out of the collection based on insertion order (First In, First Out).



 Comments   
Comment by Sam Kleinman (Inactive) [ 05/Oct/12 ]

merged

Comment by auto [ 04/Oct/12 ]

Author:

{u'date': u'2012-10-04T12:54:50-07:00', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}

Message: merge and edits: DOCS-557
Branch: master
https://github.com/mongodb/docs/commit/79a000c6e48dabf61017aee703dd5c1dd1e17ba0

Comment by auto [ 04/Oct/12 ]

Author:

{u'date': u'2012-10-02T14:00:33-07:00', u'email': u'kay.kim@10gen.com', u'name': u'kay'}

Message: DOCS-557 add ref to cloneCollectionAsCapped in convertToCapped
Branch: master
https://github.com/mongodb/docs/commit/eda1aca73321e038285f0cafb4c20ff9d4a13455

Comment by auto [ 02/Oct/12 ]

Author:

{u'date': u'2012-10-02T11:50:25-07:00', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}

Message: edits: DOCS-557
Branch: master
https://github.com/mongodb/docs/commit/800f31ea9bc9141ba93f37b5093a7b3227af830f

Comment by auto [ 02/Oct/12 ]

Author:

{u'date': u'2012-10-02T11:45:48-07:00', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}

Message: merge: DOCS-557
Branch: master
https://github.com/mongodb/docs/commit/415b26cc973a659875a46b47ee6fb9e911c9a23c

Comment by auto [ 02/Oct/12 ]

Author:

{u'date': u'2012-10-02T09:17:24-07:00', u'email': u'kay.kim@10gen.com', u'name': u'kay'}

Message: DOCS-557 add note to convertToCapped method
Branch: master
https://github.com/mongodb/docs/commit/34bcbc603bae3b5c9ab43c13d97d8901761729a6

Comment by auto [ 02/Oct/12 ]

Author:

{u'date': u'2012-10-02T08:47:19-07:00', u'email': u'kay.kim@10gen.com', u'name': u'kay'}

Message: DOCS-557 add note to convertToCapped
Branch: master
https://github.com/mongodb/docs/commit/5c7a37fec4fe27ba306f39fa0a8918cbe91215e5

Comment by Stennie Steneker (Inactive) [ 26/Sep/12 ]

scotthernandez: Thanks, updated the description.

Comment by Scott Hernandez (Inactive) [ 26/Sep/12 ]

Stephen, it will roll-over if there is more source data than room at the destination. The data "lost" will be whatever is first inserted into the dest, not the "latest" data as you suggest. It is follows $natural order then it will loose the oldest data, not the newest. It really depends on how the source query is specified – it just walks over the extents from the first doc so {$natural : 1} order.

Generated at Thu Feb 08 07:38:57 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.