Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-75760

Unify query validation behavior for cluster_find_and_modify.cpp and find_and_modify.cpp

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • 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

      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.

            Assignee:
            jason.zhang@mongodb.com Jason Zhang (Inactive)
            Reporter:
            jason.zhang@mongodb.com Jason Zhang (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: