DOCS-540 add dropTarget option to renameCollection #259
Conversation
epc
commented
Sep 24, 2012
epc
commented
- add dropTarget option
- add exceptions thrown
- rewrite to indicate that shell helper command operates within a collection but the admin command can copy a collection to a new database
Shell helper command only operates within databases, not across databases.
|
Note this also addresses DOCS-537 |
|
Scott/Ed, Is this ready for merging? Cheers, |
|
No, don't merge. There was a stub db.collection.renameCollection which I'm going to beef up and then link to from this, and remove other discussion about "shell helper" from this document. |
|
@scotthernandez can you review? I updated the helper method documentation, think I straightened out the command documentation, and removed the sentences about atomicity/speed entirely. |
|
We should add a warning that copying across databases will have a performance impact, and space requirements. It should also not be done while the source collection is being written to if a copy must be made. |
|
renameCollection appears to obtain both a write lock and global lock…wouldn't that block out the source collection being written to? |
|
Also will the space requirements be the same as the existing db + indexes or potentially larger? |
#259) * DOCSP-16529 Clarifies source/destination clusters on Quickstart * Fixes per Ashley * Fixes per Ashley * Fixes per Ajay
