[SERVER-38624] Do not allow node to startup with autoIndexId: False collection Created: 13/Dec/18 Updated: 29/Oct/23 Resolved: 15/Feb/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.9 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | Divjot Arora (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Storage NYC 2019-02-25 | ||||||||
| Participants: | |||||||||
| Description |
|
We stopped letting these collections be created in 4.0. We should stop allowing upgrades with these collections so we can assume they do not exist in 4.2 |
| Comments |
| Comment by Githook User [ 15/Feb/19 ] |
|
Author: {'name': 'Divjot Arora', 'email': 'divjot.arora@10gen.com', 'username': 'divjotarora'}Message: |
| Comment by Eric Milkie [ 12/Feb/19 ] |
|
To check for autoIndexId, look at the autoIndexId field of the CollectionOptions struct; to get the CollectionOptions, call getCollectionOptions on the CollectionCatalogEntry; there is a function to get the CollectionCatalogEntry from the Collection object. |
| Comment by Eric Milkie [ 12/Feb/19 ] |
|
To implement this, I think we should amend the ensureAllCollectionsHaveUUIDs() function to also check for this condition. There may be some system collections we need to ignore with this check; we can possible use NamespaceString::isSystem() for this. |