[SERVER-45637] Blacklist mapReduce tests that use output mode "merge" from multiversion suites Created: 17/Jan/20  Updated: 29/Oct/23  Resolved: 21/Jan/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.3.3

Type: Bug Priority: Major - P3
Reporter: Nicholas Zolnierz Assignee: Nicholas Zolnierz
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:
Linked BF Score: 50

 Comments   
Comment by Githook User [ 17/Jan/20 ]

Author:

{'name': 'Nicholas Zolnierz', 'email': 'nicholas.zolnierz@mongodb.com', 'username': 'nzolnierzmdb'}

Message: SERVER-45637 Blacklist mapReduce tests that use output mode merge from multiversion suites
Branch: master
https://github.com/mongodb/mongo/commit/c552ac4dbdee6add00194effcfc450ce25d70c6a

Comment by Nicholas Zolnierz [ 17/Jan/20 ]

Legacy mapReduce (pre-4.4) does not support output mode merge to a collection which is sharded on {_id: hashed}. All of the linked BFs will end up testing such a path for the sharded_collections_jscore_multiversion_passthrough suite, since the target collection will get dropped and recreated as sharded before the MR runs.

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