[SERVER-51844] Tenant collection cloner implicitly creates _id index while creating collection even if donor doesn't have '_id' index for that collection. Created: 27/Oct/20 Updated: 29/Oct/23 Resolved: 30/Oct/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Suganthi Mani | Assignee: | Suganthi Mani |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm-1791_milestone-B | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Repl 2020-11-02 |
| Participants: |
| Description |
|
To be noted, tenant collections are replicated collections and it's impossible to have an empty _id index. So, the problem "Tenant collection cloner implicitly creates _id index while creating collection even if donor doesn't have '_id' index for that collection." can't really happen in real world, just noticed the issue in unit testing. |
| Comments |
| Comment by Githook User [ 29/Oct/20 ] |
|
Author: {'name': 'Suganthi Mani', 'email': 'suganthi.mani@mongodb.com', 'username': 'smani87'}Message:
|
| Comment by Matthew Russotto [ 29/Oct/20 ] |
|
We do not allow replicated collections to lack an _id index. |