-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Component/s: None
-
None
Related to DRIVERS-143, obviously. DRIVERS-143 is about the Bulk API's merged results from a series of operations.
This ticket is about the simple "update" operation. If a driver uses the new "update" command, the 2.6 server responds with an accurate count of documents actually changed, in the "nModified" field. For example, if a document has "x: 1" and you use the "update" command to set x to 1, the server responds with "nModified: 0".
This behavior is impossible to simulate with OP_UPDATE, so drivers shouldn't return an nModified field as the result of a legacy update operation. Depending on the language, the field should be absent, or NULL, or attempting to access it should raise an exception.
- depends on
-
CXX-20 Implement full support for write commands
- Closed
- is related to
-
CXX-1172 Document `result::bulk_write::modified_count()` throws with mongod 2.4
- Closed
-
PHPC-278 WriteResult::getModifiedCount() should return null for legacy writes
- Closed
-
CSHARP-925 nModified should be null from legacy writes
- Closed
-
NODE-148 nModified should be null from legacy writes
- Closed
-
PYTHON-648 nModified should be null from legacy writes
- Closed
-
RUBY-727 nModified should be null from legacy writes
- Closed
- related to
-
SERVER-13001 exclude nModified from legacy write results
- Closed
-
DRIVERS-143 Don't include the nModified field in Bulk API results if talking to a legacy server.
- Closed