[DOCS-517] Include additional Limitations of Server Side JavaScript Created: 12/Sep/12 Updated: 12/Feb/13 Resolved: 12/Feb/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | mongodb-2.2 |
| Fix Version/s: | v1.1 |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Randolph Tan | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 11 years, 1 week, 1 day ago |
| Description |
|
The current doc page (http://www.mongodb.org/display/DOCS/Server-side+Code+Execution) mentions that you cannot use write operations with $eval, but it does not mention that you should not use any features that requires the Javascript engines - for example, $eval, $where, map reduce. Not sure if this is also the case for our V8 engine, but to use the Spider Monkey engine, the global Spider Monkey lock must be acquired. This means that the server will get into a dead lock if you try to call any features that uses the javascript engine. |
| Comments |
| Comment by auto [ 12/Feb/13 ] |
|
Author: {u'date': u'2013-02-12T23:54:19Z', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |