[DOCS-8203] Comment on: "manual/reference/method/db.cloneCollection.txt" Created: 03/Jul/16 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Docs Collector User (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | collector-298ba4e7, docs-triage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Location: https://docs.mongodb.com/manual/reference/method/db.cloneCollection/ |
||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 2 days ago |
| Epic Link: | DOCSP-1769 |
| Description |
|
"If you want to copy a collection from a different database name you must use the cloneCollection directly." This is EXTREMELY misleading. The cloneCollection command seems to just ignore the current database name, but it STILL copies from a db/collection to the SAME db/collection on the current server. It also doesn't return an error if the collection already exists locally – I now have some sort of half-merged collection, but the number of documents doesn't match what I was expecting |
| Comments |
| Comment by Education Bot [ 31/Oct/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |