[SERVER-9249] db object no longer available to mapper Created: 04/Apr/13 Updated: 10/Dec/14 Resolved: 07/Mar/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | MapReduce |
| Affects Version/s: | 2.4.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Doug Hudson | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
> db.serverBuildInfo() uname -a |
||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | > db.mrtest.save( {a:1,b:1}) ) > m = function () { db.other.findOne(); }> r = function (k,vaks) { } > db.mrtest.mapReduce(m, r, 'mrout') |
||||||||
| Participants: | |||||||||
| Description |
|
Referencing db in a mapper now raises an exception. The previous version I used 2.2.3 didn't do this. We rely on this to pull in extra document into when performing map reduces. A similar change happened some time ago, where the db object was no longer available to finalizers (even though the documentation implied this was valid). |
| Comments |
| Comment by Asya Kamsky [ 07/Mar/14 ] | |||||||||||||||||||
|
This was by design and is described in the release notes for 2.4 as well as the mapreduce reference page. | |||||||||||||||||||
| Comment by Pawel [ 02/May/13 ] | |||||||||||||||||||
| Comment by Carlos Monge [ 02/May/13 ] | |||||||||||||||||||
|
Replicated on version 2.4.3
|