[SERVER-80341] sharded_agg_helpers::attachCursorToPipeline should not attach dbVersion when targeting local shard by routing table Created: 23/Aug/23  Updated: 29/Oct/23  Resolved: 28/Aug/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Jordi Serra Torrens Assignee: Ivan Fefer
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
is caused by SERVER-77427 Avoid going through the network when ... Closed
Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Sprint: QE 2023-09-04
Participants:

 Description   

Here sharded_agg_helpers::attachCursorToPipeline attaches dbVersion even if we targeted by routing table. In this case, to comply with the shard versioning protocol, we only need to attach ShardVersion: X, but not dbVersion.



 Comments   
Comment by Githook User [ 28/Aug/23 ]

Author:

{'name': 'Ivan Fefer', 'email': 'ivan.fefer@mongodb.com', 'username': 'Fefer-Ivan'}

Message: SERVER-80341 In sharded_agg_helpers.cpp only attach either db version or shard version depending on the presence of routing table
Branch: master
https://github.com/mongodb/mongo/commit/961fb0c91e6cddc812b8bc8e3651dabbb8ca1b7a

Generated at Thu Feb 08 06:43:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.