[DRIVERS-143] Don't include the nModified field in Bulk API results if talking to a legacy server. Created: 05/Mar/14  Updated: 15/Apr/19  Resolved: 11/Nov/15

Status: Closed
Project: Drivers
Component/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Barrie Segal Assignee: Barrie Segal
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on JAVA-1134 BulkWriteResult.getModifiedCount shou... Closed
depends on PYTHON-647 Omit nModified field from Bulk API re... Closed
Related
is related to CSHARP-924 Don't include the nModified field in ... Closed
is related to DRIVERS-144 nModified should be null from legacy ... Closed
is related to NODE-147 Don't include the nModified field in ... Closed
is related to RUBY-726 Don't include the nModified field in ... Closed
Driver Compliance:
Key Status/Resolution FixVersion
PYTHON-647 Done 2.7
JAVA-1134 Done 2.12.0

 Description   

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().)



 Comments   
Comment by Andrew Morrow (Inactive) [ 03/Mar/15 ]

Validating for C++11 because validated for C

Generated at Thu Feb 08 08:20:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.