[SERVER-3130] m/r map/reduce functions should not allow db access Created: 23/May/11  Updated: 10/Dec/14  Resolved: 23/Apr/13

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

Type: Bug Priority: Major - P3
Reporter: Eliot Horowitz (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-8104 MapReduce on Sharded System Can Bypas... Closed
Operating System: ALL
Participants:

 Description   

access db.* shouldn't be allowed inside a map or reduce call



 Comments   
Comment by Pawel [ 02/May/13 ]

http://stackoverflow.com/questions/16344382/mongo-2-4-making-db-object-available-in-server-side-code-map-reduce

Comment by Ben Becker [ 23/Apr/13 ]

Resolved by SERVER-8104

Comment by David Whittington [ 25/May/11 ]

We are currently relying on this functionality. I can understand why you guys want to remove it, but maybe it should be made optional (you can enable this if you know what you're doing). If that's not an option I think there should be at least one release cycle where deprecation warnings are issued before removal.

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