shashank created CAMEL-26973:
--------------------------------
Summary: camel-mongodb - a DST fake world for the change streams
consumer
Key: CAMEL-26973
URL: https://issues.apache.org/jira/browse/CAMEL-26973
Project: Camel
Issue Type: Improvement
Components: camel-test, camel-mongodb
Reporter: shashank
Assignee: shashank
Part of CAMEL-26610 (tier 4). A fake world for the {{camel-mongodb}} change
streams consumer, following "Writing a fake world" in {{test-dst.adoc}}.
h3. What the world drives
* The change stream of a collection with inserts, updates, replaces and
deletes, and the resume token stored in a {{changeStreamTokenRepository}}.
* The collection dropped while the consumer reads it (drop and invalidate
events), and made again by an insert.
* A server that cannot be reached for a while: a new cursor cannot be opened, a
getMore fails, and the driver resumes the change stream itself until server
selection times out.
* Processing that fails or is slow.
* Route restarts, resuming after the stored token. (The consumer's stop waits
for its thread, which the one stack of the harness cannot run, so a restart
interrupts the consumer thread, as a forced shutdown does, and then stops and
starts the route.)
h3. Self-check
Candidates: CAMEL-25946 (the consumer stopped consuming after its collection
was dropped or renamed), CAMEL-25679 (the consumer thread ended when a new
cursor could not be opened). CAMEL-25711 and CAMEL-25607 are fixes of
{{camel-mongodb-gridfs}}, a separate module, which this world does not cover.
The fake follows the documentation of the external system (the MongoDB manual
on change streams and the Java driver), cited in the code. Per CAMEL-26610, the
world must reproduce at least one fixed bug on the code from before its fix and
pass on main. Marked with {{@DstWorld}} so the catalog and the component page
list it.
_Filed with Claude Code on behalf of allthingssecurity._
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)