[SERVER-75760] Unify query validation behavior for cluster_find_and_modify.cpp and find_and_modify.cpp Created: 06/Apr/23  Updated: 12/Jan/24  Resolved: 11/Jan/24

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

Type: Task Priority: Major - P3
Reporter: Jason Zhang Assignee: Jason Zhang
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-84751 Complete TODO listed in SERVER-75760 Closed
Assigned Teams:
Cluster Scalability
Sprint: Sharding NYC 2023-06-12, Sharding NYC 2023-06-26, Sharding NYC 2023-07-10, Sharding NYC 2023-07-24, Sharding NYC 2023-08-07, Sharding NYC 2023-08-21, Sharding NYC 2023-09-04, Sharding NYC 2023-09-18, Sharding NYC 2023-10-02, Sharding NYC 2023-10-16, Sharding NYC 2023-10-30, Cluster Scalability 2023-11-13, Cluster Scalability 2023-11-27, Cluster Scalability 2023-12-11, Cluster Scalability 2023-12-25, Cluster Scalability 2024-1-8, Cluster Scalability 2024-1-22
Participants:

 Description   

Currently, mongos relies on the shard to validate/parse a findAndModify query. If the database for an invalid findAndModify query does not exist, mongos will return an OK response with empty results instead of returning back an error due to an invalid query. This presents differing behavior when we're running in a sharded cluster vs a replica set (which would do the query validation first). To be able to achieve feature parity, we should ensure the behavior of an invalid query is the same between both configurations.



 Comments   
Comment by Githook User [ 12/Jan/24 ]

Author:

{'name': 'Jason Zhang', 'email': 'jz1242@users.noreply.github.com', 'username': 'jz1242'}

Message: SERVER-84751 Remove todo comment for SERVER-75760 (#18003)

GitOrigin-RevId: 9a27a3425e23a4698447e1c1a6311012631a4385
Branch: master
https://github.com/mongodb/mongo/commit/108e9026dfa822923e5b689e17ad86910fa46ef0

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