[SERVER-31861] when collection is created with UUID, log if UUID is new Created: 07/Nov/17 Updated: 30/Oct/23 Resolved: 09/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.0-rc4 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Judah Schvimer |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Comments |
| Comment by Githook User [ 09/Nov/17 ] |
|
Author: {'name': 'Judah Schvimer', 'username': 'judahschvimer', 'email': 'judah@mongodb.com'}Message: |
| Comment by Eric Milkie [ 08/Nov/17 ] |
|
It's confusing to me that the message will say "existing UUID" for user-provided-in-applyOps. Unless it means "existing for this collection at some point in time or place other than the present." |
| Comment by Judah Schvimer [ 08/Nov/17 ] |
|
New means that the UUID was just generated by the server and was not passed in the collection options. It won't differentiate user provided in applyOps vs. sent by a another node, but user provided is pretty rare. What ambiguity were you referring to? |
| Comment by Eric Milkie [ 07/Nov/17 ] |
|
How are you defining “new” here? |