[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:
Depends
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: SERVER-39619 Blacklist tests asserting on nMatched for multi updates in multi_stmt_txn_jscore_passthrough_with_migration
Branch: master
https://github.com/mongodb/mongo/commit/9fa4a356cc1d89adc1edd4321117503ce90e2d4b

Generated at Thu Feb 08 04:52:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.