@@ -145,6 +145,29 @@ Tag Aware Sharding
145
145
146
146
.. including tagging
147
147
148
+ Compatibility Changes
149
+ ~~~~~~~~~~~~~~~~~~~~~
150
+
151
+ .. TODO add sections here to describe compatibility changes with
152
+ regards to authentication, drivers, and mongos'
153
+
154
+ ``findAndMondify`` Returns Null value for Upserts
155
+ `````````````````````````````````````````````````
156
+
157
+ In version 2.2, for :term:`upsert` operations, :dbcommand:`findAndModify`
158
+ commands will now return the following output:
159
+
160
+ .. code-block:: javascript
161
+
162
+ {'ok': 1.0, 'value': null}
163
+
164
+ In the :program:`mongo` shell, :dbcommand:`findAndModify` operations
165
+ running as upserts will only output a ``null`` value.
166
+
167
+ Previously, in version 2.0 these operations would return an empty
168
+ document, e.g. ``{ }``.
169
+
170
+ See: :issue:`SERVER-6226`.
148
171
149
172
Naming
150
173
~~~~~~
@@ -362,21 +385,6 @@ Documentation: :ref:`sharding-shard-key-indexes`
362
385
Additional Improvements
363
386
~~~~~~~~~~~~~~~~~~~~~~~
364
387
365
- ``findAndMondify`` Returns Null value for Upserts
366
- `````````````````````````````````````````````````
367
-
368
- In 2.2, for :term:`upsert` operations, :dbcommand:`findAndModify`
369
- commands will now return the following output:
370
-
371
- .. code-block:: javascript
372
-
373
- {'ok': 1.0, 'value': null}
374
-
375
- In the :program:`mongo` shell, :dbcommand:`findAndModify` operations
376
- running as upserts will only output a ``null` value.
377
-
378
- See: :issue:`SERVER-6226`.
379
-
380
388
``_id`` Index not Required for Updates to Capped Collections
381
389
````````````````````````````````````````````````````````````
382
390
0 commit comments