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

Why do 'find' and 'aggregate' commands represent maxTimeMS differently?

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Query Optimization
    • Fully Compatible
    • QO 2023-10-02, QO 2023-10-16, QO 2023-10-30, QO 2023-11-13

      Currently FindCommandRequest and AggregateCommandRequest represent maxTimeMS differently:

      Not only is the C++ type different, but also the BSON type and the parsing/validation rules are different. For simplicity, can we make them the same? Especially since we translate 'find' requests to 'aggregate' (for views), you would think they have the same set of valid values.

      Looks like the last ticket to touch this was SERVER-54925, so there may be more discussion or explanation there.

            Assignee:
            james.harrison@mongodb.com James Harrison
            Reporter:
            david.percy@mongodb.com David Percy
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: