[SERVER-55978] Add functionality to the shell to decode a resume token Created: 09/Apr/21 Updated: 06/Dec/22 Resolved: 10/Aug/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Change streams |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Backlog - Query Execution |
| Resolution: | Won't Do | Votes: | 3 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Query Execution
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Case: | (copied to CRM) | ||||||||||||
| Description |
|
Often when diagnosing issues it is helpful to piece apart the resume token, for example to identify an offending document. The only way we have to do this right now is by writing some code or adapting one of our unit tests to run our deserializer. It would be helpful to have a function in the shell or something like that which is capable of decoding them for our use in supporting customers. |
| Comments |
| Comment by William Luo [ 10/Aug/21 ] |
|
Hi Ana and Kyle, Got it. I will follow mongosh ticket. Thanks for your response! |
| Comment by Kyle Suarez [ 10/Aug/21 ] |
|
See |
| Comment by Ana Meza [ 10/Aug/21 ] |
|
We are not adding features to the legacy shell instead we will file a ticket to add this to mongosh |
| Comment by William Luo [ 26/Jul/21 ] |
|
Is there any further information about this case? Thanks! |