[SERVER-36916] object to track index key-values that violated an index constraint Created: 29/Aug/18  Updated: 29/Oct/23  Resolved: 07/Nov/18

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.1.6

Type: Improvement Priority: Major - P3
Reporter: Eric Milkie Assignee: Louis Williams
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-37267 Implement Constraint violation tracke... Closed
Related
Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2018-10-22, Storage NYC 2018-11-05, Storage NYC 2018-11-19
Participants:
Linked BF Score: 0

 Description   

Several facilities could benefit from a common object that tracks index table insertions that violate a constraint while an index's constraints are temporarily disabled: both the new Hybrid Index and Initial Sync could benefit from such an object. This object would collect index keys that violated constraints, and could dump them out at a later time so that each index key entry in the index could be checked to see that the constraints are no longer violated.



 Comments   
Comment by Githook User [ 08/Nov/18 ]

Author:

{'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}

Message: SERVER-36916 Use signed int for _id BSON value in DuplicateKeyTracker
Branch: master
https://github.com/mongodb/mongo/commit/7f89f8d1748766f90d142f86e6d10e3435833d5d

Comment by Githook User [ 07/Nov/18 ]

Author:

{'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}

Message: SERVER-36916 Object to keep track of keys that violate uniqueness constraints
Branch: master
https://github.com/mongodb/mongo/commit/8c3ff92b1a17fb0d64995ef21e534dae3bd20010

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