mongo 2.15.0 → 2.17.0

data/spec/spec_tests/data/crud_unified/findOneAndDelete-let.yml

@@ -0,0 +1,88 @@
+description: "findOneAndDelete-let"
+
+schemaVersion: "1.0"
+
+createEntities:
+  - client:
+      id: &client0 client0
+      observeEvents: [ commandStartedEvent ]
+  - database:
+      id: &database0 database0
+      client: *client0
+      databaseName: &database0Name crud-tests
+  - collection:
+      id: &collection0 collection0
+      database: *database0
+      collectionName: &collection0Name coll0
+
+initialData: &initialData
+  - collectionName: *collection0Name
+    databaseName: *database0Name
+    documents:
+      - { _id: 1 }
+      - { _id: 2 }
+
+tests:
+  - description: "findOneAndDelete with let option"
+    runOnRequirements:
+      - minServerVersion: "5.0"
+    operations:
+      - name: findOneAndDelete
+        object: *collection0
+        arguments:
+          filter: &filter
+            $expr:
+              $eq: [ "$_id", "$$id" ]
+          let: &let0
+            id: 1
+    expectEvents:
+      - client: *client0
+        events:
+          - commandStartedEvent:
+              command:
+                findAndModify: *collection0Name
+                query: *filter
+                remove: true
+                let: *let0
+    outcome:
+      -
+        collectionName: *collection0Name
+        databaseName: *database0Name
+        documents:
+          - { _id: 2 }
+
+  - description: "findOneAndDelete with let option unsupported (server-side error)"
+    runOnRequirements:
+      - minServerVersion: "4.2.0"
+        maxServerVersion: "4.4.99"
+    operations:
+      - name: findOneAndDelete
+        object: *collection0
+        arguments:
+          filter: &filter1
+            $expr:
+              $eq: [ "$_id", "$$id" ]
+          let: &let1
+            id: 1
+        expectError:
+          # This error message is consistent between 4.2.x and 4.4.x servers.
+          # Older servers return a different error message.
+          errorContains: "field 'let' is an unknown field"
+          isClientError: false
+    expectEvents:
+      - client: *client0
+        events:
+          - commandStartedEvent:
+              command:
+                findAndModify: *collection0Name
+                query: *filter1
+                remove: true
+                let: *let1
+    outcome:
+      -
+        collectionName: *collection0Name
+        databaseName: *database0Name
+        documents:
+          - { _id: 1 }
+          - { _id: 2 }
+

data/spec/spec_tests/data/crud_unified/findOneAndReplace-let.yml

@@ -0,0 +1,94 @@
+description: "findOneAndReplace-let"
+
+schemaVersion: "1.0"
+
+createEntities:
+  - client:
+      id: &client0 client0
+      observeEvents: [ commandStartedEvent ]
+  - database:
+      id: &database0 database0
+      client: *client0
+      databaseName: &database0Name crud-tests
+  - collection:
+      id: &collection0 collection0
+      database: *database0
+      collectionName: &collection0Name coll0
+
+initialData: &initialData
+  - collectionName: *collection0Name
+    databaseName: *database0Name
+    documents:
+      - { _id: 1 }
+      - { _id: 2 }
+
+tests:
+  - description: "findOneAndReplace with let option"
+    runOnRequirements:
+      - minServerVersion: "5.0"
+    operations:
+      - name: findOneAndReplace
+        object: *collection0
+        arguments:
+          filter: &filter
+            $expr:
+              $eq: [ "$_id", "$$id" ]
+          replacement: &replacement
+            x: "x"
+          let: &let0
+            id: 1
+        expectResult:
+          _id: 1
+    expectEvents:
+      - client: *client0
+        events:
+          - commandStartedEvent:
+              command:
+                findAndModify: *collection0Name
+                query: *filter
+                update: *replacement
+                let: *let0
+    outcome:
+      -
+        collectionName: *collection0Name
+        databaseName: *database0Name
+        documents:
+          - { _id: 1, x: "x" }
+          - { _id: 2 }
+
+  - description: "findOneAndReplace with let option unsupported (server-side error)"
+    runOnRequirements:
+      - minServerVersion: "4.2.0"
+        maxServerVersion: "4.4.99"
+    operations:
+      - name: findOneAndReplace
+        object: *collection0
+        arguments:
+          filter: &filter1
+            $expr:
+              $eq: [ "$_id", "$$id" ]
+          replacement: &replacement1
+            x: "x"
+          let: &let1
+            id: 1
+        expectError:
+          # This error message is consistent between 4.2.x and 4.4.x servers.
+          # Older servers return a different error message.
+          errorContains: "field 'let' is an unknown field"
+          isClientError: false
+    expectEvents:
+      - client: *client0
+        events:
+          - commandStartedEvent:
+              command:
+                findAndModify: *collection0Name
+                query: *filter1
+                update: *replacement1
+                let: *let1
+    outcome:
+      -
+        collectionName: *collection0Name
+        databaseName: *database0Name
+        documents:
+          - { _id: 1 }
+          - { _id: 2 }

data/spec/spec_tests/data/crud_unified/findOneAndUpdate-let.yml

@@ -0,0 +1,96 @@
+description: "findOneAndUpdate-let"
+
+schemaVersion: "1.0"
+
+createEntities:
+  - client:
+      id: &client0 client0
+      observeEvents: [ commandStartedEvent ]
+  - database:
+      id: &database0 database0
+      client: *client0
+      databaseName: &database0Name crud-tests
+  - collection:
+      id: &collection0 collection0
+      database: *database0
+      collectionName: &collection0Name coll0
+
+initialData: &initialData
+  - collectionName: *collection0Name
+    databaseName: *database0Name
+    documents:
+      - { _id: 1 }
+      - { _id: 2 }
+
+tests:
+  - description: "findOneAndUpdate with let option"
+    runOnRequirements:
+      - minServerVersion: "5.0"
+    operations:
+      - name: findOneAndUpdate
+        object: *collection0
+        arguments:
+          filter: &filter
+            $expr:
+              $eq: [ "$_id", "$$id" ]
+          update: &update
+            - $set: {x: "$$x" }
+          let: &let0
+            id: 1
+            x: "foo"
+        expectResult:
+          _id: 1
+    expectEvents:
+      - client: *client0
+        events:
+          - commandStartedEvent:
+              command:
+                findAndModify: *collection0Name
+                query: *filter
+                update: *update
+                let: *let0
+    outcome:
+      -
+        collectionName: *collection0Name
+        databaseName: *database0Name
+        documents:
+          - { _id: 1, x: "foo" }
+          - { _id: 2 }
+
+  - description: "findOneAndUpdate with let option unsupported (server-side error)"
+    runOnRequirements:
+      - minServerVersion: "4.2.0"
+        maxServerVersion: "4.4.99"
+    operations:
+      - name: findOneAndUpdate
+        object: *collection0
+        arguments:
+          filter: &filter1
+            $expr:
+              $eq: [ "$_id", "$$id" ]
+          update: &update1
+            - $set: {x: "$$x"}
+          let: &let1
+            id: 1
+            x: "foo"
+        expectError:
+          # This error message is consistent between 4.2.x and 4.4.x servers.
+          # Older servers return a different error message.
+          errorContains: "field 'let' is an unknown field"
+          isClientError: false
+    expectEvents:
+      - client: *client0
+        events:
+          - commandStartedEvent:
+              command:
+                findAndModify: *collection0Name
+                query: *filter1
+                update: *update1
+                let: *let1
+    outcome:
+      -
+        collectionName: *collection0Name
+        databaseName: *database0Name
+        documents:
+          - { _id: 1 }
+          - { _id: 2 }

data/spec/spec_tests/data/crud_unified/updateMany-let.yml

@@ -0,0 +1,103 @@
+description: "updateMany-let"
+
+schemaVersion: "1.0"
+
+createEntities:
+  - client:
+      id: &client0 client0
+      observeEvents: [ commandStartedEvent ]
+  - database:
+      id: &database0 database0
+      client: *client0
+      databaseName: &database0Name crud-tests
+  - collection:
+      id: &collection0 collection0
+      database: *database0
+      collectionName: &collection0Name coll0
+
+initialData: &initialData
+  - collectionName: *collection0Name
+    databaseName: *database0Name
+    documents:
+      - { _id: 1 }
+      - { _id: 2, name: "name" }
+      - { _id: 3, name: "name"  }
+
+
+tests:
+  - description: "updateMany with let option"
+    runOnRequirements:
+      - minServerVersion: "5.0"
+    operations:
+      - name: updateMany
+        object: *collection0
+        arguments:
+          filter: &filter
+            $expr:
+              $eq: [ "$name", "$$name" ]
+          update: &update
+            - $set: {x: "$$x", y: "$$y" }
+          let: &let0
+            name: name
+            x: foo
+            y: { $literal: "bar" }
+        expectResult:
+          matchedCount: 2
+          modifiedCount: 2
+          upsertedCount: 0
+    expectEvents:
+      - client: *client0
+        events:
+          - commandStartedEvent:
+              command:
+                update: *collection0Name
+                updates:
+                  -
+                    q: *filter
+                    u: *update
+                let: *let0
+    outcome:
+      -
+        collectionName: *collection0Name
+        databaseName: *database0Name
+        documents:
+          - { _id: 1 }
+          - { _id: 2, name: "name", x: "foo", y: "bar" }
+          - { _id: 3, name: "name", x: "foo", y: "bar" }
+
+  - description: "updateMany with let option unsupported (server-side error)"
+    runOnRequirements:
+      - minServerVersion: "3.6.0"
+        maxServerVersion: "4.4.99"
+    operations:
+      - name: updateMany
+        object: *collection0
+        arguments:
+          filter: &filter1
+            _id: 1
+          update: &update1
+            - $set: {x: "$$x"}
+          let: &let1
+            x: foo
+        expectError:
+          errorContains: "'update.let' is an unknown field"
+          isClientError: false
+    expectEvents:
+      - client: *client0
+        events:
+          - commandStartedEvent:
+              command:
+                update: *collection0Name
+                updates:
+                  -
+                    q: *filter1
+                    u: *update1
+                let: *let1
+    outcome:
+      -
+        collectionName: *collection0Name
+        databaseName: *database0Name
+        documents:
+          - { _id: 1 }
+          - { _id: 2, name: "name" }
+          - { _id: 3, name: "name" }

data/spec/spec_tests/data/crud_unified/updateOne-let.yml

@@ -0,0 +1,98 @@
+description: "updateOne-let"
+
+schemaVersion: "1.0"
+
+createEntities:
+  - client:
+      id: &client0 client0
+      observeEvents: [ commandStartedEvent ]
+  - database:
+      id: &database0 database0
+      client: *client0
+      databaseName: &database0Name crud-tests
+  - collection:
+      id: &collection0 collection0
+      database: *database0
+      collectionName: &collection0Name coll0
+
+initialData: &initialData
+  - collectionName: *collection0Name
+    databaseName: *database0Name
+    documents:
+      - { _id: 1 }
+      - { _id: 2 }
+
+tests:
+  - description: "UpdateOne with let option"
+    runOnRequirements:
+      - minServerVersion: "5.0"
+    operations:
+      - name: updateOne
+        object: *collection0
+        arguments:
+          filter: &filter
+            $expr:
+              $eq: [ "$_id", "$$id" ]
+          update: &update
+            - $set: {x: "$$x" }
+          let: &let0
+            id: 1
+            x: "foo"
+        expectResult:
+          matchedCount: 1
+          modifiedCount: 1
+          upsertedCount: 0
+    expectEvents:
+      - client: *client0
+        events:
+          - commandStartedEvent:
+              command:
+                update: *collection0Name
+                updates:
+                  -
+                    q: *filter
+                    u: *update
+                let: *let0
+    outcome:
+      -
+        collectionName: *collection0Name
+        databaseName: *database0Name
+        documents:
+          - { _id: 1, x: "foo" }
+          - { _id: 2 }
+
+  - description: "UpdateOne with let option unsupported (server-side error)"
+    runOnRequirements:
+      - minServerVersion: "3.6.0"
+        maxServerVersion: "4.4.99"
+    operations:
+      - name: updateOne
+        object: *collection0
+        arguments:
+          filter: &filter1
+            _id: 1
+          update: &update1
+            - $set: {x: "$$x"}
+          let: &let1
+            x: foo
+        expectError:
+          errorContains: "'update.let' is an unknown field"
+          isClientError: false
+    expectEvents:
+      - client: *client0
+        events:
+          - commandStartedEvent:
+              command:
+                update: *collection0Name
+                updates:
+                  -
+                    q: *filter1
+                    u: *update1
+                let: *let1
+    outcome:
+      -
+        collectionName: *collection0Name
+        databaseName: *database0Name
+        documents:
+          - { _id: 1 }
+          - { _id: 2 }

data/spec/spec_tests/data/load_balancers/event-monitoring.yml

@@ -0,0 +1,99 @@
+description: monitoring events include correct fields
+
+schemaVersion: '1.3'
+
+runOnRequirements:
+  - topologies: [ load-balanced ]
+
+createEntities:
+  - client:
+      id: &client0 client0
+      useMultipleMongoses: true
+      uriOptions:
+        retryReads: false
+      observeEvents:
+        - commandStartedEvent
+        - commandSucceededEvent
+        - commandFailedEvent
+        - poolClearedEvent
+  - database:
+      id: &database0 database0
+      client: *client0
+      databaseName: &database0Name database0
+  - collection:
+      id: &collection0 collection0
+      database: *database0
+      collectionName: &collection0Name coll0
+
+initialData:
+  - databaseName: *database0Name
+    collectionName: *collection0Name
+    documents: []
+
+tests:
+  - description: command started and succeeded events include serviceId
+    operations:
+      - name: insertOne
+        object: *collection0
+        arguments:
+          document: { x: 1 }
+    expectEvents:
+      - client: *client0
+        events:
+          - commandStartedEvent:
+              commandName: insert
+              hasServiceId: true
+          - commandSucceededEvent:
+              commandName: insert
+              hasServiceId: true
+
+  - description: command failed events include serviceId
+    operations:
+      - name: find
+        object: *collection0
+        arguments:
+          filter: { $or: true }
+        expectError:
+          isError: true
+    expectEvents:
+      - client: *client0
+        events:
+          - commandStartedEvent:
+              commandName: find
+              hasServiceId: true
+          - commandFailedEvent:
+              commandName: find
+              hasServiceId: true
+
+  - description: poolClearedEvent events include serviceId
+    operations:
+      - name: failPoint
+        object: testRunner
+        arguments:
+          client: *client0
+          failPoint:
+            configureFailPoint: failCommand
+            mode: { times: 1 }
+            data:
+              failCommands: [find]
+              closeConnection: true
+      - name: find
+        object: *collection0
+        arguments:
+          filter: {}
+        expectError:
+          isClientError: true
+    expectEvents:
+      - client: *client0
+        events:
+          - commandStartedEvent:
+              commandName: find
+              hasServiceId: true
+          - commandFailedEvent:
+              commandName: find
+              hasServiceId: true
+      - client: *client0
+        eventType: cmap
+        events:
+          - poolClearedEvent:
+              hasServiceId: true

data/spec/spec_tests/data/load_balancers/lb-connection-establishment.yml

@@ -0,0 +1,36 @@
+description: connection establishment for load-balanced clusters
+
+schemaVersion: '1.3'
+
+runOnRequirements:
+  - topologies: [ load-balanced ]
+
+createEntities:
+  - client:
+      id: &client0 client0
+      uriOptions:
+        # Explicitly set loadBalanced to false to override the option from the global URI.
+        loadBalanced: false
+      observeEvents:
+        - commandStartedEvent
+  - database:
+      id: &database0 database0
+      client: *client0
+      databaseName: &database0Name database0
+
+tests:
+  - description: operations against load balancers fail if URI contains loadBalanced=false
+    skipReason: servers have not implemented LB support yet so they will not fail the connection handshake in this case
+    operations:
+      - name: runCommand
+        object: *database0
+        arguments:
+          commandName: ping
+          command: { ping: 1 }
+        expectError:
+          isClientError: false
+    expectEvents:
+      # No events should be published because the server fails the connection handshake, so the "ping" command is never
+      # sent.
+      - client: *client0
+        events: []

data/spec/spec_tests/data/load_balancers/non-lb-connection-establishment.yml

@@ -0,0 +1,56 @@
+description: connection establishment if loadBalanced is specified for non-load balanced clusters
+
+schemaVersion: '1.3'
+
+runOnRequirements:
+  # Don't run on replica sets because the URI used to configure the clients will contain multiple hosts and the
+  # replicaSet option, which will cause an error when constructing the lbTrueClient entity.
+  - topologies: [ single, sharded ]
+
+createEntities:
+  - client:
+      id: &lbTrueClient lbTrueClient
+      # Restrict to a single mongos to ensure there are not multiple hosts in the URI, which would conflict with
+      # loadBalanced=true.
+      useMultipleMongoses: false
+      uriOptions:
+        loadBalanced: true
+  - database:
+      id: &lbTrueDatabase lbTrueDatabase
+      client: *lbTrueClient
+      databaseName: &lbTrueDatabaseName lbTrueDb
+  - client:
+      id: &lbFalseClient lbFalseClient
+      uriOptions:
+        loadBalanced: false
+  - database:
+      id: &lbFalseDatabase lbFalseDatabase
+      client: *lbFalseClient
+      databaseName: &lbFalseDatabaseName lbFalseDb
+
+_yamlAnchors:
+  runCommandArguments:
+    - &pingArguments
+      arguments:
+        commandName: ping
+        command: { ping: 1 }
+
+tests:
+  # These tests assert that drivers behave correctly if loadBalanced=true/false for non-load balanced clusters. Existing
+  # spec tests should cover the case where loadBalanced is unset.
+
+  # If the server is not configured to be behind a load balancer and the URI contains loadBalanced=true, the driver
+  # should error during the connection handshake because the server's hello response does not contain a serviceId field.
+  - description: operations against non-load balanced clusters fail if URI contains loadBalanced=true
+    operations:
+      - name: runCommand
+        object: *lbTrueDatabase
+        <<: *pingArguments
+        expectError:
+          errorContains: Driver attempted to initialize in load balancing mode, but the server does not support this mode
+
+  - description: operations against non-load balanced clusters succeed if URI contains loadBalanced=false
+    operations:
+      - name: runCommand
+        object: *lbFalseDatabase
+        <<: *pingArguments