[SERVER-57081] Creating a collection through `applyOps` fails with a `CannotImplicitlyCreateCollection` exception Created: 20/May/21  Updated: 29/Oct/23  Resolved: 21/May/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.0.0-rc1, 5.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Fixed Votes: 0
Labels: post-rc0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v5.0
Participants:

 Description   

As part of SERVER-52778 we added calls to ScopedAllowImplicitCollectionCreate_UNSAFE for all the places, which can create collection. The one, which was missed was that for applyOps.

Without this, any invocation of applyOps with an operation, which creates a collection will fail. Since applyOps is used internally by the Cloud team, we should add the scoped object entry there as well.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 03/Jun/21 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-57081 Enable collection creation through applyOps

(cherry picked from commit 400e776707024c0a548031436dbd7c53b58c17b7)
Branch: v5.0
https://github.com/mongodb/mongo/commit/f175495dfa94bca30b8d1b4788dd86f57da96232

Comment by Githook User [ 21/May/21 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-57081 Enable collection creation through applyOps
Branch: master
https://github.com/mongodb/mongo/commit/400e776707024c0a548031436dbd7c53b58c17b7

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