Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-6047

Ignore read/write concern in applySession for Atlas Search Index Helpers

XMLWordPrintableJSON

    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?

      Use Case

      As an... Atlas user
      I want... Atlas commands to not fail if I'm using an explicit session with a read/write concern specified
      So that... I can reuse my sessions for non-Atlas specific and Atlas specific operations.

      Unknowns

      • How do we not add readConcern / writeConcern to a listSearchIndexes command since its commandName is 'aggregate'?

      Acceptance Criteria

      Implementation Requirements

      • update applySession so that in the following cases a read/write concern is not appended to the command object
        • snapshot = true

      Testing Requirements

      Documentation Requirements

      • DOCSP ticket, API docs, etc

      Follow up requirements:

      • Add a common drivers test to cover this scenario

            Assignee:
            Unassigned Unassigned
            Reporter:
            aditi.khare@mongodb.com Aditi Khare
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: