[SERVER-64556] coll_mod_takes_collection_x_lock.js collection name collision Created: 16/Mar/22 Updated: 29/Oct/23 Resolved: 16/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Yujin Kang Park | Assignee: | Yujin Kang Park |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Execution Team 2022-03-21 | ||||
| Participants: | |||||
| Linked BF Score: | 62 | ||||
| Description |
|
After adding the assertion on createCollection, the common "foo" collection name results in collection exists failure. |
| Comments |
| Comment by Githook User [ 16/Mar/22 ] |
|
Author: {'name': 'Yu Jin Kang Park', 'email': 'yujin.kang@mongodb.com', 'username': 'ykangpark'}Message: |