[JAVA-1263] Handle Bulk API edge case for pre-2.6 servers when upserted _id not returned Created: 05/Jun/14 Updated: 23/Jul/14 Resolved: 25/Jun/14 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Write Operations |
| Affects Version/s: | None |
| Fix Version/s: | 2.12.3, 3.0.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Barrie Segal | Assignee: | Ross Lawley |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
Server versions before 2.6 only return the 'upserted' field in an update result when the upserted _id is an ObjectId. If the user provides any other value for _id in the query spec, or update document (for a replace operation) the upserted field is not returned. This causes invalid counts for nUpserted in the Bulk API result set. The purpose of this ticket is to work around the issue in the Java driver. In all of these examples the server upserts a new document but does not return the _id of the document inserted:
|
| Comments |
| Comment by Githook User [ 25/Jun/14 ] |
|
Author: {u'username': u'rozza', u'name': u'Ross Lawley', u'email': u'ross.lawley@gmail.com'}Message: Fix reporting _id for Bulk API edge case for pre-2.6 servers When upserted _id is not returned on custom _id's
|
| Comment by Githook User [ 18/Jun/14 ] |
|
Author: {u'username': u'rozza', u'name': u'Ross Lawley', u'email': u'ross.lawley@gmail.com'}Message: Fix reporting _id for Bulk API edge case for pre-2.6 servers When upserted _id is not returned on custom _id's
|