[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:
Backports
Depends
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: SERVER-50475 Put data on both shards in mr_noscripting.js

(cherry picked from commit e213ad984d8f72560ab14bb63c0c7dbdb9cc4efa)
Branch: v4.4
https://github.com/mongodb/mongo/commit/c21f819b43459cfec98ea880b8c6e22a414fa956

Comment by Githook User [ 28/Aug/20 ]

Author:

{'name': 'David Percy', 'email': 'david.percy@mongodb.com', 'username': 'dpercy'}

Message: SERVER-50475 Put data on both shards in mr_noscripting.js
Branch: master
https://github.com/mongodb/mongo/commit/e213ad984d8f72560ab14bb63c0c7dbdb9cc4efa

Generated at Thu Feb 08 05:22:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.