[DOCS-3866] Docs should strongly advise against use of db.eval() Created: 04/Aug/14  Updated: 16/Mar/15  Resolved: 03/Oct/14

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: v1.3.12

Type: Bug Priority: Major - P3
Reporter: William Zola Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to DOCS-3916 Create stronger warning for db.foo.co... Closed
Participants:
Days since reply: 9 years, 28 weeks, 2 days ago

 Description   

In general, using db.eval() or the $eval command is a Very Bad idea. The docs should discourage its use, and encourage the use of client-side operations (possibly with projection) instead.

Problems with $eval:

  • Acquires the global lock
  • Cannot be used in a sharded environment
  • Requires __system privilege
  • Non-performant since it runs in JavaScript

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