[SERVER-1715] shouldn't be able to access database from m/r finalize Created: 01/Sep/10 Updated: 12/Jul/16 Resolved: 01/Sep/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | 1.7.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eliot Horowitz (Inactive) | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
We would have to get a write lock for the op, which would make it very slow. |
| Comments |
| Comment by Serge Matveenko [ 27/Jul/11 ] |
|
It seems that reading DB in finalize is very useful feature. Say you have MapReduce that counts wins and looses by various boxing fighters. But the boxers start there fighting career from different years. And to know the best one it is useful to divide win count by number of years the boxer was fighting. And that is why you need to just look for boxer career start date in boxers collection in finalize function that is not accessable at all now. |
| Comment by auto [ 01/Sep/10 ] |
|
Author: {'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}Message: don't allow db access in m/r finalize |
| Comment by auto [ 01/Sep/10 ] |
|
Author: {'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}Message: Scope::rename and ability to block db access prep for |
| Comment by auto [ 01/Sep/10 ] |
|
Author: {'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}Message: don't allow db access in m/r finalize |
| Comment by auto [ 01/Sep/10 ] |
|
Author: {'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}Message: Scope::rename and ability to block db access prep for |