[SERVER-28531] Fix convert-to-capped to use new UUID Created: 28/Mar/17 Updated: 06/Dec/17 Resolved: 29/Mar/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Geert Bosch | Assignee: | Geert Bosch |
| Resolution: | Done | 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-04-17 | ||||||||
| Participants: | |||||||||
| Description |
|
The convertToCapped operation is essentially a copy of (part of) the existing collection to a new collection, followed by a rename of that collection over the original collection. So, we should make sure to use a new UUID. |
| Comments |
| Comment by Githook User [ 29/Mar/17 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}Message: |