[SERVER-85383] Add placementConflictTime to local and remote requests Created: 18/Jan/24  Updated: 05/Feb/24  Resolved: 05/Feb/24

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

Type: Improvement Priority: Major - P3
Reporter: Jordi Olivares Provencio Assignee: Jordi Olivares Provencio
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-85163 Modify setup of TransactionRouter Closed
Related
related to SERVER-86223 Complete TODO listed in SERVER-85383 Closed
Backwards Compatibility: Fully Compatible
Sprint: CAR Team 2024-01-22, CAR Team 2024-02-05
Participants:

 Description   

Right now both local and remote requests of a pipeline do not propagate the placementConflictTime to the shards.

We should propagate it so that transactions fail when they should.



 Comments   
Comment by Githook User [ 05/Feb/24 ]

Author:

{'name': 'Jordi Olivares Provencio', 'email': 'jordi.olivares-provencio@mongodb.com', 'username': 'jordiolivares'}

Message: SERVER-85383 Propagate placementConflictTime through the aggregation pipeline (#18186)

GitOrigin-RevId: 296ef040c387a8925330205d18c248ac68dff40f
Branch: master
https://github.com/mongodb/mongo/commit/0f1450f373c771bb64431c038b383f6c2ab8279b

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