[SERVER-57133] Update expected result for jstests/replsets/batch_write_command_wc.js Created: 21/May/21 Updated: 29/Oct/23 Resolved: 02/Jun/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc1, 5.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Svilen Mihaylov (Inactive) | Assignee: | Alya Berciu |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v5.0
|
||||||||
| Sprint: | Query Optimization 2021-06-14 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 82 | ||||||||
| Description |
|
Code was recently introduced to allow the insertion of documents containing $-prefixed fields, such that the document {$invalid: 'doc'} is no longer actually invalid. This is why n=2 instead of 1 like we expect in this test. The solution should be to change {$invalid: 'doc'} in the test to something like {_id: /a/}, which is still considered an invalid document, so that we can still test inserting one valid/ one invalid document with the invalid write concern. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 04/Jun/21 ] |
|
Author: {'name': 'Alya Berciu', 'email': 'alyacarina@gmail.com', 'username': 'alyacb'}Message: |
| Comment by Githook User [ 02/Jun/21 ] |
|
Author: {'name': 'Alya Berciu', 'email': 'alyacarina@gmail.com', 'username': 'alyacb'}Message: |