[SERVER-47581] mongoS does not set 'useNewUpsert' on $mergeCursors pipelines [4.4, 4.2] Created: 16/Apr/20 Updated: 29/Oct/23 Resolved: 22/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.7, 4.4.0-rc3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Bernard Gorman | Assignee: | Bernard Gorman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Backport Requested: |
v4.2
|
||||||||||||||||
| Sprint: | Query 2020-04-20, Query 2020-05-04 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 50 | ||||||||||||||||
| Description |
|
In However, in cases where a $merge is sent to a shard as part of a $mergeCursors pipeline, the 'useNewUpsert' flag is not set on the command. In these scenarios, the old incorrect behaviour is still observed. |
| Comments |
| Comment by Githook User [ 04/May/20 ] |
|
Author: {'name': 'Bernard Gorman', 'email': 'bernard.gorman@gmail.com', 'username': 'gormanb'}Message: (cherry picked from commit dda2fb45cbf624c9270f8fad7f3c5c5a2f0834eb) |
| Comment by Githook User [ 22/Apr/20 ] |
|
Author: {'name': 'Bernard Gorman', 'email': 'bernard.gorman@gmail.com', 'username': 'gormanb'}Message: |