[SERVER-46751] Remove useNewUpsert from aggregation_request.cpp in 4.7 Created: 10/Mar/20  Updated: 29/Oct/23  Resolved: 19/Aug/21

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

Type: Task Priority: Major - P3
Reporter: Bernard Gorman Assignee: Adi Agrawal
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-56366 Update FCV constants in server code b... Closed
Backwards Compatibility: Fully Compatible
Sprint: Query Execution 2021-06-28, Query Execution 2021-07-12, Query Execution 2021-07-26, QE 2021-08-09, QE 2021-08-23
Participants:

 Description   

In 4.6 we removed all occurrences of useNewUpsert, with one exception: AggregationRequest can still ingest useNewUpsert, in order to facilitate upgrading from 4.4 to 4.6. This last vestige of useNewUpsert should be removed during the 4.7 development cycle.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 19/Aug/21 ]

Author:

{'name': 'Adityavardhan Agrawal', 'email': 'adi.agrawal@mongodb.com'}

Message: SERVER-46751 remove useNewUpsert
Branch: master
https://github.com/mongodb/mongo/commit/a774156ecde60e8122660eb2df39170c973c642c

Comment by Eric Cox (Inactive) [ 28/Jun/21 ]

This is blocked until SERVER-56366 is merged since the last-lts param in the shell needs to point to 5.0. See page 6 in 

https://docs.google.com/document/d/1RMrJwLofhknDKNHSmyqw6W_g9ysgmWT9VGrJ8tqkmvg/edit#heading=h.k2corm2ga1b6

Comment by David Storch [ 13/Mar/20 ]

Since we don't have "4.7 Required" yet, I'm marking this as "4.5 Required". We should update it to "4.7 Required" when that fixVersion becomes available.

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