This is related to SERVER-13001. In that ticket it was decided to not report nModified if a legacy shard primary is part of an update operation. It would appear that the changes for that ticket also removed nModified if a write error occurs (e.g. duplicate key error), even with a standalone mongod. nModified should be 0 in this case, just like 'n'.
This change makes it hard for drivers to differentiate when they should not report nModified (the result was at least in part from a legacy server) and when they should (all other cases).
- is depended on by
-
DRIVERS-145 Don't include the nModified field in Bulk API results if talking to a legacy server via mongos
- Closed
- is related to
-
SERVER-13001 exclude nModified from legacy write results
- Closed