[SERVER-65025] Always include the collection UUID in the change stream resumeToken Created: 29/Mar/22 Updated: 02/Apr/22 Resolved: 02/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Arun Banala | Assignee: | Mickey Winters |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | pm1950-m4 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | QE 2022-04-04, QE 2022-04-18 | ||||||||
| Participants: | |||||||||
| Description |
|
The collection UUID field is ordered before the 'eventIdentifier', so if we want to log the 'eventIdentifier', we also needed the UUID to be present. For certain operations, like dropDatabase or events on view, the UUID is absent. We should use a null value for these cases. |