[SERVER-45538] Implement and test shard version retry logic for $unionWith sub-pipeline Created: 13/Jan/20  Updated: 29/Oct/23  Resolved: 26/Feb/20

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

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

Issue Links:
Depends
depends on SERVER-45526 Support union with sharded collections Closed
depends on SERVER-45838 Rename/restructure mongo_process_inte... Closed
is depended on by SERVER-45712 Remove flag guard for $unionWith Closed
Duplicate
is duplicated by SERVER-38758 Avoid restarting $lookup from the top... Closed
Problem/Incident
causes SERVER-57483 Results from $lookup stage are not ca... Closed
causes SERVER-57579 DocumentSourceSequentialCache doesn't... Closed
Related
is related to SERVER-38758 Avoid restarting $lookup from the top... Closed
Backwards Compatibility: Fully Compatible
Sprint: Query 2020-02-10, Query 2020-02-24, Query 2020-03-09
Participants:

 Description   

Specifically if the cache on mongos for the union'ed collection is stale, the $unionWith should retry it's sub-pipeline only instead of the entire base aggregation.



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

Author:

{'name': 'Charlie Swanson', 'username': 'cswanson310', 'email': 'charlie.swanson@mongodb.com'}

Message: SERVER-45538 Add shard version retry logic for $unionWith sub-pipeline
Branch: master
https://github.com/mongodb/mongo/commit/27363455aaba930778a5feff02b0b320d4b850af

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