[SERVER-45967] Upgrade/downgrade behavior and testing for $out/$merge on secondaries Created: 04/Feb/20  Updated: 29/Oct/23  Resolved: 26/Mar/20

Status: Closed
Project: Core Server
Component/s: Aggregation Framework
Affects Version/s: None
Fix Version/s: 4.4.0-rc0

Type: Task Priority: Major - P3
Reporter: David Storch Assignee: Mihai Andrei
Resolution: Fixed Votes: 0
Labels: qexec-team
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.4
Sprint: Query 2020-02-24, Query 2020-03-09, Query 2020-03-23, Query 2020-04-06
Participants:
Case:

 Description   

Add an FCV check so that an attempt to invoke $out/$merge in a mixed-version replica set will always return a useful error message when the read preference is non-primary. If the operation targets a binary version 4.4 node in FCV "4.2", then this new FCV check should trip. If the operation targets a binary version 4.2 node, then the operation will fail with a 'NotMaster' category error, just as it would in 4.2 and all previous versions.



 Comments   
Comment by Githook User [ 26/Mar/20 ]

Author:

{'name': 'Mihai Andrei', 'email': 'mihai.andrei@mongodb.com'}

Message: SERVER-45967 Upgrade/downgrade behavior and testing for $out/$merge on secondaries
Branch: v4.4
https://github.com/mongodb/mongo/commit/7bff3f32f8d1f2a00bc5138f0203cbb75ae1869e

Comment by David Storch [ 05/Mar/20 ]

This patch should only go into 4.4, not master, so I've updated the fixVersion "4.4 Required".

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