[SERVER-7489] db.foo.copyTo() uses db.eval() which isn't lock-friendly Created: 26/Oct/12  Updated: 09/Mar/15  Resolved: 09/Mar/15

Status: Closed
Project: Core Server
Component/s: Shell
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Dwight Merriman Assignee: Unassigned
Resolution: Duplicate Votes: 3
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
duplicates SERVER-17478 Remove or modify copyTo() shell helper Closed
Related
related to DOCS-3916 Create stronger warning for db.foo.co... Closed
related to SERVER-12742 remove collection.copyTo test shell h... Closed
Participants:

 Description   

We should do something. At a minimum let the user know it locks a lot.
It's listed in the help so could be used quite a bit. Also does it not work sharded? And if not, that is not documented?



 Comments   
Comment by J Rassi [ 09/Mar/15 ]

Resolving as duplicate of SERVER-17478.

Comment by Paulie Pena [ 25/Jul/14 ]

The documentation of copyTo() should also reference the database command "eval" (http://docs.mongodb.org/manual/reference/command/eval/). The docs for db.eval() do reference the "nolock" option of the database command "eval", but since the names are sooo similar, the distinction should probably be referenced any place where db.eval() is referenced.

Comment by Bogomir Engel [ 19/Aug/13 ]

Basically it's not documented at all, apart from API reference for the C# Driver. It's merely listed in the help() output.

Just for reference, there's a snippet in the docs showing how this is supposed to be done currently.

Generated at Thu Feb 08 03:14:41 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.