mongodb 1.1.1

The official MongoDB driver for Rust
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74

runOn:
    -
        minServerVersion: "3.6"
        topology: ["replicaset"]

data:
    - { _id: 1, x: 11 }

tests:
    -
        description: "InsertMany succeeds after one network error"
        failPoint:
            configureFailPoint: onPrimaryTransactionalWrite
            mode: { times: 1 }
        operation:
            name: "insertMany"
            arguments:
                documents:
                    - { _id: 2, x: 22 }
                    - { _id: 3, x: 33 }
                options: { ordered: true }
        outcome:
            result:
                insertedIds: { 0: 2, 1: 3 }
            collection:
                data:
                    - { _id: 1, x: 11 }
                    - { _id: 2, x: 22 }
                    - { _id: 3, x: 33 }
    -
        description: "InsertMany with unordered execution"
        failPoint:
            configureFailPoint: onPrimaryTransactionalWrite
            mode: { times: 1 }
        operation:
            name: "insertMany"
            arguments:
                documents:
                    - { _id: 2, x: 22 }
                    - { _id: 3, x: 33 }
                options: { ordered: false }
        outcome:
            result:
                insertedIds: { 0: 2, 1: 3 }
            collection:
                data:
                    - { _id: 1, x: 11 }
                    - { _id: 2, x: 22 }
                    - { _id: 3, x: 33 }
    -
        description: "InsertMany fails after multiple network errors"
        failPoint:
            # Normally, a mongod will insert the documents as a batch with a
            # single commit. If this fails, mongod may try to insert each
            # document one at a time depending on the failure. Therefore our
            # single insert command may trigger the failpoint twice on each
            # driver attempt. This test permanently enables the fail point to
            # ensure the retry attempt always fails.
            configureFailPoint: onPrimaryTransactionalWrite
            mode: "alwaysOn"
            data: { failBeforeCommitExceptionCode: 1 }
        operation:
            name: "insertMany"
            arguments:
                documents:
                    - { _id: 2, x: 22 }
                    - { _id: 3, x: 33 }
                    - { _id: 4, x: 44 }
                options: { ordered: true }
        outcome:
            error: true
            collection:
                data:
                    - { _id: 1, x: 11 }