-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Component/s: None
-
None
Clarification to the Bulk API: We should not include the nModified field in Bulk API results if we're talking to a legacy server.
Prior, it was left unspecified whether nModified should be included or not when talking to a legacy server. Now, we're saying it should definitely not be included. If your language is constrained such that you must include the field, then user code should get an exception when accessing the field if you're talking to a legacy server.
(This ticket is only about merging results with the Bulk API. DRIVERS-144 is about results from a single direct call to Collection.update().)
- depends on
-
JAVA-1134 BulkWriteResult.getModifiedCount should throw if server version < 2.6
- Closed
-
PYTHON-647 Omit nModified field from Bulk API results if legacy server
- Closed
- is related to
-
CSHARP-924 Don't include the nModified field in Bulk API results if talking to a legacy server.
- Closed
-
DRIVERS-144 nModified should be null from legacy writes
- Closed
-
NODE-147 Don't include the nModified field in Bulk API results if talking to a legacy server.
- Closed
-
RUBY-726 Don't include the nModified field in Bulk API results if talking to a legacy server.
- Closed