Skip to content

Commit a331304

Browse files
authored
Docsp-28053- write concerns (#157)
* fix write concern * db feedback
1 parent 124ddd0 commit a331304

File tree

1 file changed

+14
-23
lines changed

1 file changed

+14
-23
lines changed

source/configuration/write.txt

Lines changed: 14 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -73,11 +73,11 @@ The following options for writing to MongoDB are available:
7373
- ``insert``: insert the data.
7474
- ``replace``: replace an existing document that matches the
7575
``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
7777
inserts a new document.
7878
- ``update``: update an existing document that matches the
7979
``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
8181
inserts a new document.
8282

8383
|
@@ -96,25 +96,16 @@ The following options for writing to MongoDB are available:
9696
| **Default:** ``_id``
9797

9898
* - ``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.
108104
|
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``
115106

116107
* - ``writeConcern.journal``
117-
- | Specifies ``j``, a write concern option to enable request for
108+
- | Specifies ``j``, a write-concern option to enable request for
118109
acknowledgment that the data is confirmed on on-disk journal for
119110
the criteria specified in the ``w`` option. You can specify
120111
either ``true`` or ``false``.
@@ -124,9 +115,9 @@ The following options for writing to MongoDB are available:
124115
:manual:`WriteConcern j option </reference/write-concern/#j-option>`.
125116

126117
* - ``writeConcern.wTimeoutMS``
127-
- | Specifies ``wTimeoutMS``, a write concern option to return an error
118+
- | Specifies ``wTimeoutMS``, a write-concern option to return an error
128119
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.
130121
|
131122
| For more information on ``wTimeoutMS`` values, see the MongoDB server
132123
guide on the
@@ -140,9 +131,9 @@ The following options for writing to MongoDB are available:
140131
``false``.
141132
|
142133
| **Default:** ``true``
143-
134+
144135
* - ``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
146137
into BSON.
147138
|
148139
| **Default:** ``false``
@@ -174,7 +165,7 @@ settings:
174165

175166
If you specify a setting both in the ``connection.uri`` and in a separate
176167
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
178169
database for the connection is ``foobar``:
179170

180171
.. code:: cfg

0 commit comments

Comments
 (0)