[SERVER-12664] Change nUpdated to nMatched in bulk api results Created: 10/Feb/14 Updated: 22/Feb/14 Resolved: 14/Feb/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Shell |
| Affects Version/s: | None |
| Fix Version/s: | 2.6.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Daniel Pasette (Inactive) | Assignee: | Randolph Tan |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
Currently the bulk api returns the fields nUpdated, which indicates the number of documents which were matched by the update query and nModified, which indicates the number of documents modified by the update (does not include no-ops). This ticket is to change nUpdated to nMatched. |
| Comments |
| Comment by Gary Murakami [ 13/Feb/14 ] |
|
I had previously mentioned the inconsistency of nModified versus nDocsModified. Thanks to the description above mentioning nModified, I now know that this has beeen resolved, and that I need to edit the Ruby driver. Other drivers also please take note to that nDocsModified has been replaced with nModified and edit appropriately. |
| Comment by Githook User [ 13/Feb/14 ] |
|
Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: |
| Comment by Githook User [ 13/Feb/14 ] |
|
Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: |