[SERVER-30481] Schema upgrade/downgrade needs to handle dropped collections Created: 02/Aug/17 Updated: 30/Oct/23 Resolved: 02/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.11 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Geert Bosch | Assignee: | Geert Bosch |
| 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: | Storage 2017-08-21 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
The schema upgrade/downgrade code should check if a collection still exist after locking it. |
| Comments |
| Comment by Githook User [ 10/Aug/17 ] |
|
Author: {'name': 'Geert Bosch', 'email': 'geert@mongodb.com'}Message: |
| Comment by Max Hirschhorn [ 08/Aug/17 ] |
|
https://github.com/mongodb/mongo/commit/34081bb4536f2a7961ed9d22278b2e31aad362a5 |