[SERVER-61913] Investigate tracking deletes for unique index conversion Created: 03/Dec/21  Updated: 29/Oct/23  Resolved: 19/Jan/22

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

Type: Task Priority: Major - P3
Reporter: Benety Goh Assignee: Benety Goh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-61486 Investigate work needed to track dupl... Closed
is related to SERVER-62431 [POC] Enforce uniqueness constraint e... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-01-24
Participants:

 Description   

In the implementation for SERVER-61486, we avoid tracking delete operations because of the way we record these operations through the OpObserver framework. If we had a robust scheme for observing committed deletes along with inserts and updates, we may be able to conflate some of these operations to reduce the number of index searches prior to converting the index to be unique.



 Comments   
Comment by Benety Goh [ 19/Jan/22 ]

No functional change. We decided that the work in the TODO comment was no longer relevant.

Comment by Githook User [ 13/Jan/22 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-61913 remove TODO
Branch: master
https://github.com/mongodb/mongo/commit/c7f44d7db67cf4b12db5e1a30c1d83dc9308a11c

Comment by Benety Goh [ 13/Jan/22 ]

We are considering rejecting potential duplicates at an earlier stage of the unique index conversion in SERVER-62431. Very likely this work will no longer be necessary.

Generated at Thu Feb 08 05:53:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.