[DRIVERS-145] Don't include the nModified field in Bulk API results if talking to a legacy server via mongos Created: 10/Mar/14 Updated: 27/May/22 Resolved: 04/Oct/16 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | A. Jesse Jiryu Davis | Assignee: | Barrie Segal |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Server Compat: | 2.6 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Driver Compliance: |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
In In In this ticket, we sometimes omit nModified when executing the Bulk API against mongos 2.6 in a mixed-version cluster. According to If the client does a series of "update" commands within the same bulk operation against the same mongos, some responses could include nModified and some won't, depending on which mongods the mongos sent the operation to. mongos follows this principle: nModified is 0 if you know it's 0. It's N if you know it's N. It's omitted or NULL if you don't know its true value. Drivers must follow this principle too. The driver algorithm for merging results, when using write commands, follows in pseudocode:
If you're merging results from the Bulk API when using legacy ops, of course, nModified is already omitted according to If you like, you can wait until This is going to require an additional QA ticket for all drivers. |
| Comments |
| Comment by Andrew Morrow (Inactive) [ 03/Mar/15 ] |
|
Validating for C++11 because validated for C |