[SERVER-39619] Blacklist tests that assert on nMatched for multi updates in multi_stmt_txn_jscore_passthrough_with_migration Created: 15/Feb/19 Updated: 29/Oct/23 Resolved: 21/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.10 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding 2019-03-25 | ||||
| Participants: | |||||
| Linked BF Score: | 7 | ||||
| Description |
|
In transactions, updates with multi=true are versioned and not always broadcast to all shards, unlike outside transactions, but update still does not filter orphan documents, so nMatched may include orphans and be larger than expected for all tests in multi_stmt_txn_jscore_passthrough_with_migration. This includes jstests/core/index_arr2.js and possibly others. |
| Comments |
| Comment by Githook User [ 21/Mar/19 ] |
|
Author: {'email': 'jack.mulrow@mongodb.com', 'name': 'Jack Mulrow', 'username': 'jsmulrow'}Message: |