[DOCS-4061] Comment on: "manual/reference/command/cloneCollectionAsCapped.txt" Created: 18/Sep/14 Updated: 08/Dec/16 Resolved: 10/Oct/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.12 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Docs Collector User (Inactive) | Assignee: | Andrew Aldridge |
| Resolution: | Done | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
MongoDB V2.6.4 64bits, Windows 7 64bits Location: http://docs.mongodb.org/manual/reference/command/cloneCollectionAsCapped/#dbcmd.cloneCollectionAsCapped |
||
| Participants: | |
| Days since reply: | 9 years, 18 weeks, 5 days ago |
| Description |
|
At the bottom of this page If the capped size specified for the new collection is smaller than the size of the original uncapped collection, then MongoDB will begin overwriting earlier documents in insertion order, which is first in, first out (e.g “FIFO”). Then I tried below:
No data have been overwritten in capped collection aa even though I specified a capped size which is smaller than the original collection's. |
| Comments |
| Comment by Githook User [ 10/Oct/14 ] |
|
Author: {u'username': u'i80and', u'name': u'Andrew Aldridge', u'email': u'i80and@foxquill.com'}Message: Signed-off-by: Sam Kleinman <samk@10gen.com> |