[SERVER-78370] Refactor targetUpdate and targetDelete to check if a query should use the two phase write protocol Created: 22/Jun/23  Updated: 29/Oct/23  Resolved: 01/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: Jason Zhang Assignee: Jason Zhang
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
Backwards Compatibility: Fully Compatible
Sprint: Sharding NYC 2023-06-26, Sharding NYC 2023-07-10, Sharding NYC 2023-07-24, Sharding NYC 2023-08-07
Participants:
Linked BF Score: 105

 Description   

Currently there exists a supplementary helper that checks whether or not we need to use the two phase write protocol for a write without a shard key. This helper re-parses the query into a CanonicalQuery, which adds undesirable overhead to write operations. This check can likely be done in targetUpdate()/targetDelete() directly so we don't incur this excess latency.



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

Author:

{'name': 'Jason Zhang', 'email': 'jason.zhang@mongodb.com', 'username': 'jz1242'}

Message: SERVER-78370 Refactor targetUpdate and targetDelete to check if a query should use the two phase write protocol
Branch: minh.luu-no_compile_sys-perf
https://github.com/mongodb/mongo/commit/5174bb20659ada0b141ba929cc96fd3164fa7628

Comment by Githook User [ 31/Jul/23 ]

Author:

{'name': 'Jason Zhang', 'email': 'jason.zhang@mongodb.com', 'username': 'jz1242'}

Message: SERVER-78370 Refactor targetUpdate and targetDelete to check if a query should use the two phase write protocol
Branch: master
https://github.com/mongodb/mongo/commit/5174bb20659ada0b141ba929cc96fd3164fa7628

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