Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-11833

Docs for SERVER-35388: Improve misleading error messages for aggregation stages banned in transactions

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Gone away
    • None
    • 4.0.1, 4.1.1
    • manual, Server
    • None

    Description

      ----------------------------

      Original Description

      Description:

      No documentation summary in engineering ticket

      Engineering Ticket Description:

      The error messages vary for the aggregation stages not allowed in transactions, as tested in read_concern_snapshot_aggregation.js. Since the readConcern level is upconverted to "snapshot" for transactions, and some of these stages only work with particular readConcern levels, they may error due to the readConcern, which could cause a user to think that the transaction would succeed if they specify a different readConcern level. It would be more helpful to provide an error message that the stage is banned in transactions.

      Examples:

      "errmsg" : "Aggregation stage $listLocalSessions requires read concern local but
      found { readConcern: { level: \"snapshot\" } }",
       
      "errmsg" : "$out can not be used with either a 'majority' or 'snapshot' read
      concern level",
      

      ----------------------------

      Description

      Scope of changes (files that need work and how much)

      Impact to other docs outside of this product

      MVP (work and date?)

      Resources (e.g. Scope Docs, Invision)

      Attachments

        Activity

          People

            Unassigned Unassigned
            kay.kim@mongodb.com Kay Kim (Inactive)
            Kay Kim Kay Kim (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              4 years, 24 weeks, 1 day ago