[SERVER-31749] Clarify the reason temporary unique collection names are made Created: 27/Oct/17 Updated: 30/Oct/23 Resolved: 01/Dec/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.2, 3.7.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Benety Goh |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Repl 2018-01-01 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
We use "makeUniqueCollectionNamespace" to make collection namespaces with random unused names. We often call them "tmp<random>", which doesn't say what they're used for (https://github.com/mongodb/mongo/blob/cdef5d9ad7a5c138637354a0644457a439507b80/src/mongo/db/catalog/create_collection.cpp#L165). It would be helpful if we added a prefix or suffix to each of these to say if it's for a create, rename, rollback, or convertToCapped. |
| Comments |
| Comment by Githook User [ 28/Dec/17 ] |
|
Author: {'username': 'benety', 'email': 'benety@mongodb.com', 'name': 'Benety Goh'}Message: (cherry picked from commit bd20a3fe5a8aea410282f25f7dacdf7bb923b7c0) |
| Comment by Githook User [ 01/Dec/17 ] |
|
Author: {'name': 'Benety Goh', 'username': 'benety', 'email': 'benety@mongodb.com'}Message: |
| Comment by Judah Schvimer [ 27/Oct/17 ] |
|
If we're concerned about long collection names, we could just append 1 character to the beginning of each namespace and have a legend specifying what type of operation that character corresponds to. |