[SERVER-13905] MapReduce to empty capped collection results in NON-capped collection Created: 12/May/14 Updated: 08/Mar/16 Resolved: 08/Mar/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | MapReduce |
| Affects Version/s: | 2.4.10, 2.6.0 |
| Fix Version/s: | 3.1.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Avi Levy | Assignee: | Daniel Pasette (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Minor Change |
| Operating System: | ALL |
| Steps To Reproduce: | db.input.drop() ) db.createCollection("cap", {capped:true,size:100000}) //M/R to non empty capped collection ) ) |
| Participants: |
| Description |
|
When doing a map reduce where the out collection is an empty capped collection and the out method of reduce, the result is a non-capped collection. |
| Comments |
| Comment by Mathias Stearn [ 08/Mar/16 ] |
|
This was fixed as part of |
| Comment by J Rassi [ 12/May/14 ] |
|
Confirmed with 2.4.10, 2.6.1. Assigning to dan@10gen.com for triage. |