[SERVER-41140] All usages of MultiIndexBlock should ensure callers check for duplicate key constraints Created: 14/May/19  Updated: 29/Oct/23  Resolved: 19/Jun/19

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.3.1, 4.2.2

Type: Bug Priority: Major - P3
Reporter: Louis Williams Assignee: Gregory Wlodarek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.2
Sprint: Execution Team 2019-06-03, Execution Team 2019-06-17, Execution Team 2019-07-01
Participants:
Linked BF Score: 11

 Description   

Rather than invariant that there are no entries in the duplicate key constraint table, we should also invariant that users of the MultiIndexBlock call checkConstraints() at least once.

This will identify the usages of MultiIndexBlock that aren't resilient to handling duplicate key errors, which should also be fixed in this ticket.



 Comments   
Comment by Githook User [ 16/Oct/19 ]

Author:

{'name': 'Gregory Wlodarek', 'username': 'GWlodarek', 'email': 'gregory.wlodarek@mongodb.com'}

Message: SERVER-41140 All usages of MultiIndexBlock should ensure callers check for duplicate key constraints

(cherry picked from commit 0d462c7be0462ad27f68c056145de712bee65684)
Branch: v4.2
https://github.com/mongodb/mongo/commit/e3c2926205997f66978e162f6d987f8d3674cf93

Comment by Githook User [ 19/Jun/19 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-41140 All usages of MultiIndexBlock should ensure callers check for duplicate key constraints
Branch: master
https://github.com/mongodb/mongo/commit/0d462c7be0462ad27f68c056145de712bee65684

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