Decides whether to differentiate write and read operations for aggregate commands when using defaultMaxTimeMS

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0, 8.0.0-rc4
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • v8.0
    • CAR Team 2024-04-01, CAR Team 2024-04-15
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Pipeline command returns its ReadWriteType always as read regardless the piepline stages it has https://github.com/10gen/mongo/blob/b25e6075140e1bd6851b513480ce34a6504d1969/src/mongo/db/commands/pipeline_command.cpp#L339. We should decide if we want to skip using the defaultMaxTimeMS for aggregate commands that have a write stage.

            Assignee:
            Yuhong Zhang
            Reporter:
            Yuhong Zhang
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: