[SERVER-50475] mr_noscripting.js can fail spuriously on new mapReduce implementation Created: 21/Aug/20 Updated: 29/Oct/23 Resolved: 09/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0, 4.4.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Percy | Assignee: | David Percy |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v4.4
|
||||||||
| Participants: | |||||||||
| Linked BF Score: | 35 | ||||||||
| Description |
|
This test confirms that the "noscripting" param causes the mapReduce command to fail. It does this by setting the param on one of the two shards. But the way the test sets up the data, sometimes the "noscripting" shard is empty, and the new mapReduce implementation doesn't need to talk to it. So we should make sure the test puts data on both shards. |
| Comments |
| Comment by Githook User [ 14/Jan/21 ] |
|
Author: {'name': 'David Percy', 'email': 'david.percy@mongodb.com', 'username': 'dpercy'}Message: (cherry picked from commit e213ad984d8f72560ab14bb63c0c7dbdb9cc4efa) |
| Comment by Githook User [ 28/Aug/20 ] |
|
Author: {'name': 'David Percy', 'email': 'david.percy@mongodb.com', 'username': 'dpercy'}Message: |