[SERVER-36768] Orphaned collection recovery should allow recovered collections to be renamed Created: 20/Aug/18 Updated: 29/Oct/23 Resolved: 23/Aug/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.3, 4.1.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Xiangyu Yao (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | nyc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Backport Requested: |
v4.0
|
||||
| Sprint: | Storage NYC 2018-08-27 | ||||
| Participants: | |||||
| Description |
|
When a collection that is in the storage engine but orphaned from the catalog gets recovered, we create a new collection with the "local.system.orphan-[ident]" namespace. This is problematic because show collections does not show collections that a user does not own. An attempt to rename the collection to a user namespace returns an error because the source starts with ".system" |
| Comments |
| Comment by Githook User [ 18/Sep/18 ] |
|
Author: {'name': 'Xiangyu Yao', 'email': 'xiangyu.yao@mongodb.com', 'username': 'xy24'}Message: (cherry picked from commit 238af0b7739e6c4702e234cfb28e3a714f119523) |
| Comment by Githook User [ 23/Aug/18 ] |
|
Author: {'name': 'Xiangyu Yao', 'email': 'xiangyu.yao@mongodb.com', 'username': 'xy24'}Message: |