[SERVER-29914] Correctly propagate new UUID for renaming across databases Created: 28/Jun/17 Updated: 30/Oct/23 Resolved: 05/Jul/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.10 |
| 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 | ||
| Backwards Compatibility: | Fully Compatible | |
| Operating System: | ALL | |
| Steps To Reproduce: |
|
|
| Sprint: | Storage 2017-07-10 | |
| Participants: |
| Description |
|
When enabling collection UUIDs, and renaming collections across databases, correctly pass through the UUID from the oplog entry, so primary and secondary will maintain identical UUIDs. |
| Comments |
| Comment by Githook User [ 05/Jul/17 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}Message: |
| Comment by Githook User [ 05/Jul/17 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}Message: |