[SERVER-36930] Remove test specific to 4.1 dev cycle $out changes Created: 29/Aug/18  Updated: 06/Dec/22  Resolved: 21/Aug/19

Status: Closed
Project: Core Server
Component/s: Aggregation Framework, Upgrade/Downgrade
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Charlie Swanson Assignee: Backlog - Query Team (Inactive)
Resolution: Duplicate Votes: 0
Labels: open_todo_in_code, todo_in_code
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-42794 Update Query-related generic upgrade/... Closed
Related
is related to SERVER-36381 Serialize $out to old format if featu... Closed
Assigned Teams:
Query
Participants:

 Description   

As part of SERVER-36381 we added a test to stress running an $out during the 4.0 -> 4.2 upgrade. This test can be removed once we branch for 4.2 since it was targeted at making sure the cluster can correctly handle the "legacy" {$out: "name"}-style syntax even though it is internally upgraded to the newer: {$out: {to: "name", ...}} syntax internally. Once we're only concerned with the 4.2 -> 4.4 upgrade, all versions will understand both syntaxes, so this test can be removed.



 Comments   
Comment by David Storch [ 07/Sep/18 ]

ian.whalen, under the new JIRA workflow, in what state should a ticket like this sit? Can we use "4.3 Required"?

Generated at Thu Feb 08 04:44:29 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.