@@ -73,11 +73,11 @@ The following options for writing to MongoDB are available:
73
73
- ``insert``: insert the data.
74
74
- ``replace``: replace an existing document that matches the
75
75
``idFieldList`` value with the new data. If no match exists, the
76
- value of ``upsertDocument`` indicates whether or not the connector
76
+ value of ``upsertDocument`` indicates whether the connector
77
77
inserts a new document.
78
78
- ``update``: update an existing document that matches the
79
79
``idFieldList`` value with the new data. If no match exists, the
80
- value of ``upsertDocument`` indicates whether or not the connector
80
+ value of ``upsertDocument`` indicates whether the connector
81
81
inserts a new document.
82
82
83
83
|
@@ -96,25 +96,16 @@ The following options for writing to MongoDB are available:
96
96
| **Default:** ``_id``
97
97
98
98
* - ``writeConcern.w``
99
- - | Specifies ``w``, a write concern option to acknowledge the level to
100
- which the change propagated in the MongoDB replica set. You can
101
- specify one of the following values:
102
-
103
- - ``MAJORITY``
104
- - ``W1``, ``W2``, or ``W3``
105
- - ``ACKNOWLEDGED``
106
- - ``UNACKNOWLEDGED``
107
-
99
+ - | Specifies ``w``, a write-concern option to request acknowledgment
100
+ that the write operation has propogated to a specified number of
101
+ MongoDB instances. For a list
102
+ of allowed values for this option, see :manual:`WriteConcern
103
+ </reference/write-concern/#w-option>` in the MongoDB manual.
108
104
|
109
- | For more information on ``w`` values, see the MongoDB server guide on
110
- the :manual:`WriteConcern w option
111
- </reference/write-concern/#w-option>`.
112
-
113
- |
114
- | **Default:** ``ACKNOWLEDGED``
105
+ | **Default:** ``1``
115
106
116
107
* - ``writeConcern.journal``
117
- - | Specifies ``j``, a write concern option to enable request for
108
+ - | Specifies ``j``, a write- concern option to enable request for
118
109
acknowledgment that the data is confirmed on on-disk journal for
119
110
the criteria specified in the ``w`` option. You can specify
120
111
either ``true`` or ``false``.
@@ -124,9 +115,9 @@ The following options for writing to MongoDB are available:
124
115
:manual:`WriteConcern j option </reference/write-concern/#j-option>`.
125
116
126
117
* - ``writeConcern.wTimeoutMS``
127
- - | Specifies ``wTimeoutMS``, a write concern option to return an error
118
+ - | Specifies ``wTimeoutMS``, a write- concern option to return an error
128
119
when a write operation exceeds the number of milliseconds. If you
129
- use this optional setting, you must specify a non-negative integer.
120
+ use this optional setting, you must specify a nonnegative integer.
130
121
|
131
122
| For more information on ``wTimeoutMS`` values, see the MongoDB server
132
123
guide on the
@@ -140,9 +131,9 @@ The following options for writing to MongoDB are available:
140
131
``false``.
141
132
|
142
133
| **Default:** ``true``
143
-
134
+
144
135
* - ``convertJson``
145
- - | When ``true``, the connector parses the string and converts extended JSON
136
+ - | When ``true``, the connector parses the string and converts extended JSON
146
137
into BSON.
147
138
|
148
139
| **Default:** ``false``
@@ -174,7 +165,7 @@ settings:
174
165
175
166
If you specify a setting both in the ``connection.uri`` and in a separate
176
167
configuration, the ``connection.uri`` setting overrides the separate
177
- setting. For example, given the following configuration, the
168
+ setting. For example, in the following configuration, the
178
169
database for the connection is ``foobar``:
179
170
180
171
.. code:: cfg
0 commit comments