[SERVER-6558] findAndModify should take a write concern Created: 23/Jul/12 Updated: 08/May/17 Resolved: 01/Sep/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Write Ops |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 16 |
| Labels: | commands, findAndModify | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | Sharding 1 04/03/15, Sharding 2 04/24/15, Sharding 3 05/15/15, Sharding 4 06/05/15, Sharding 5 06/26/16 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
The findAndModify should support specification of a writeConcern, in the same manner as the write commands (insert, update, delete), and should support returning write concern failures in the same manner, as well. EDIT 8/31/15 The ticket describing the work for extending support for this to all commands which write can be found in All commands that perform writes on behalf of users should support specification of a writeConcern, in the same manner as the write commands (insert, update, delete), and should support returning write concern failures in the same manner, as well. |
| Comments |
| Comment by Githook User [ 27/Mar/15 ] |
|
Author: {u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'siyuan.zhou@mongodb.com'}Message: |
| Comment by Githook User [ 27/Mar/15 ] |
|
Author: {u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'siyuan.zhou@mongodb.com'}Message: |
| Comment by Githook User [ 17/Mar/15 ] |
|
Author: {u'username': u'alabid', u'name': u'Daniel Alabi', u'email': u'alabidan@gmail.com'}Message: |
| Comment by Githook User [ 16/Mar/15 ] |
|
Author: {u'username': u'alabid', u'name': u'Daniel Alabi', u'email': u'alabidan@gmail.com'}Message: Revert " This reverts commit bb9b4e27c8c31542af52d80f4c3751c435909d69. |
| Comment by Githook User [ 16/Mar/15 ] |
|
Author: {u'username': u'alabid', u'name': u'Daniel Alabi', u'email': u'alabidan@gmail.com'}Message: |
| Comment by Antoine Girbal [ 09/Oct/14 ] |
|
Most implementation of "transactions" require use of findAndModify, but with w=1 it’s really not viable with possible rollbacks |
| Comment by Eric Milkie [ 30/Jan/14 ] |
|
Note: write commands and user management commands already take a write concern. We should come up with a standard for this and apply it to all commands which do writing. |
| Comment by Yuri Finkelstein [ 02/Nov/12 ] |
|
for instance, findAndModify must be able to support write concern with w:2 just like the regular update would do. |