[SERVER-6719] cloneCollection should allow parsing a namespace Created: 06/Aug/12 Updated: 11/Jul/16 Resolved: 04/Sep/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Shell |
| Affects Version/s: | 2.0.6, 2.2.0-rc0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andre de Frere | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
The documentation for the cloneCollection command tells users to use a namespace of a collection, however we just prepend the current database name to the string they input. This means that the cloneCollection command will try and clone the incorrect database name if they follow the docs and use a fully qualified namespace name. For example: db.cloneCollection("localhost:27017", "test.some_collection") will try and clone the collection test.test.some_collection when it is run from test |
| Comments |
| Comment by Ramon Fernandez Marina [ 04/Sep/14 ] |
|
This is now properly documented. |