[SERVER-63907] Remove code or fix comment referring to handling MMAP Created: 23/Feb/22  Updated: 29/Oct/23  Resolved: 18/Apr/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.1.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) 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-27246 Running applyOps with an op on a none... Closed
is related to SERVER-30830 applyOps should return NamespaceNotFo... Closed
is related to SERVER-33192 Delete apply_ops_atomicity.js Closed
is related to SERVER-41496 Remove Database::getCollection method Closed
is related to SERVER-33182 Remove atomic applyOps Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-05-02
Participants:

 Description   

This code.



 Comments   
Comment by Githook User [ 18/Apr/22 ]

Author:

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

Message: SERVER-63907 remove redundant database lookup from atomic applyOps
Branch: master
https://github.com/mongodb/mongo/commit/394c5bd97ab6f939f59b9012dcdb67dc79c95751

Comment by Benety Goh [ 15/Apr/22 ]

This DatabaseHolder check is made redundant by SERVER-41496 which no longer requires the Database object to locate the collection.

The CollectionCatalog lookup will lead to the same NamespaceNotFound result when using applyOps to run CRUD ops in a non-existent namespace.

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