Hello Camel developers, My name is Michal Wolski, and I work as a data integration engineer at Pollin Electronic GmbH (Germany). I would like to start contributing to the Camel codebase and was looking for guidance on a potential improvement.
While working with the camel-mongodb component (MongoDB change streams), I noticed that the resume token used for resuming change stream consumption appears to be managed internally (in ChangeStreamsThread) and is not exposed via endpoint configuration or exchange metadata. This makes it difficult to implement restart/resume scenarios where a route may be temporarily down and later restarted without losing the ability to continue from the last processed change stream position. Would it be reasonable to expose the resume token in a way that allows users to persist and re-inject it on restart? If so, I would be happy to work on a JIRA issue and contribute a patch, but I would appreciate guidance on the preferred Camel design approach for this (e.g., headers vs. state repository vs. other extension points). I already have a JIRA account on issues.apache.org. Thanks for your time, Michal Wolski
