[SERVER-66017] Always include operationDescription in v2 resume token for "rename" events Created: 27/Apr/22 Updated: 29/Oct/23 Resolved: 28/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc4, 6.1.0-rc0 |
| Type: | Improvement | Priority: | Blocker - P1 |
| Reporter: | Bernard Gorman | Assignee: | Arun Banala |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm1950-m6 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v6.0
|
||||
| Sprint: | QE 2022-05-02 | ||||
| Participants: | |||||
| Description |
|
At present, we do not generate the operationDescription for rename events if showExpandedEvents is false. But this means that we also don't include it in the resume token, which is both inconsistent with other events AND means that we will generate a different resume token based on the value of showExpandedEvents, which should not be the case. We should always include the operationDescription in the resume token, whether or not we include it in the event body itself. |
| Comments |
| Comment by Githook User [ 28/Apr/22 ] |
|
Author: {'name': 'Arun Banala', 'email': 'arun.banala@mongodb.com', 'username': 'banarun'}Message: (cherry picked from commit 6d0743c76fd5c7fc7aa018ac043e3adc983a7c16) |
| Comment by Githook User [ 28/Apr/22 ] |
|
Author: {'name': 'Arun Banala', 'email': 'arun.banala@mongodb.com', 'username': 'banarun'}Message: |