[SERVER-43267] Fail MapReduce when source collection is the same as destination collection Created: 11/Sep/19 Updated: 29/Oct/23 Resolved: 16/Oct/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jacob Evans | Assignee: | Mihai Andrei |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Query 2019-10-21 |
| Participants: |
| Description |
|
This will likely fail already because $out and $merge do not support outputting to the source collection but we should produce a nice error message. |
| Comments |
| Comment by Githook User [ 16/Oct/19 ] |
|
Author: {'name': 'Mihai Andrei', 'email': 'mihai.andrei@mongodb.com'}Message: |
| Comment by Charlie Swanson [ 11/Sep/19 ] |
|
I’m pretty sure $out will let you output to the original namespace because it’s writing to a temp me in the meantime. Is there any evidence that this is broken in the current mapReduce implementation? We may have to lift this restriction for $merge in this one case. |