[SERVER-60733] Test create collection after drop collection Created: 15/Oct/21  Updated: 29/Oct/23  Resolved: 15/Feb/22

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

Type: Improvement Priority: Major - P3
Reporter: Tommaso Tocci Assignee: Allison Easton
Resolution: Fixed Votes: 0
Labels: shardingemea-qw
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2021-11-01, Sharding EMEA 2021-11-15, Sharding EMEA 2021-11-29, Sharding EMEA 2021-12-13, Sharding EMEA 2021-12-27, Sharding EMEA 2022-01-10, Sharding EMEA 2022-01-24, Sharding EMEA 2022-02-07, Sharding EMEA 2022-02-21
Participants:
Linked BF Score: 50
Story Points: 3

 Description   

This ticket is to add a test case to ensure that a drop collection once completed won't delete any documents on a subsequent recreated collection.
This has to run in the stepdown suite.



 Comments   
Comment by Githook User [ 15/Feb/22 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-60733 Test create collection after drop collection
Branch: master
https://github.com/mongodb/mongo/commit/eeff4a62ad0702abfe3d599e16696baefc6c8cec

Comment by Githook User [ 15/Feb/22 ]

Author:

{'name': 'Daniel Gottlieb', 'email': 'daniel.gottlieb@mongodb.com', 'username': 'dgottlieb'}

Message: Revert "SERVER-60733 Test create collection after drop collection"

This reverts commit 7aa7f8f47a2c8e07fdfb5f79b9adf870b7ca6612.
Branch: master
https://github.com/mongodb/mongo/commit/f68e19f425a944e6c2f66566eb38eb0f9233dcc8

Comment by Githook User [ 14/Feb/22 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-60733 Test create collection after drop collection
Branch: master
https://github.com/mongodb/mongo/commit/7aa7f8f47a2c8e07fdfb5f79b9adf870b7ca6612

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