[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: |
|
||||
| Participants: | |||||
| Days since reply: | 11 years, 19 weeks, 5 days ago | ||||
| Description |
|
Add a note to: http://docs.mongodb.org/manual/reference/command/convertToCapped/
|
| 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: |
| 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: |
| 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: |
| 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: |
| 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: |
| 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: |
| 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. |