-
Type:
Bug
-
Resolution: Won't Do
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Change streams
-
None
-
Query Execution
-
ALL
-
(copied to CRM)
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.
- is duplicated by
-
SERVER-82330 Ability to decode change stream resume tokens in JS tests
-
- Closed
-
- related to
-
SERVER-32283 Add an expression to inspect the resume token of a change stream
-
- Closed
-
-
MONGOSH-946 Add functionality to mongosh to decode a resume token
-
- Closed
-