Skip to content

feat(change_stream): MultiStream impl of ChangeStream - #643

Draft
matt-codecov wants to merge 1 commit into
mainfrom
matt/change-stream-multistream
Draft

matt-codecov wants to merge 1 commit into
mainfrom
matt/change-stream-multistream

Conversation

@matt-codecov

Copy link
Copy Markdown
Contributor

not currently used. demo of how ChangeStreamFactory can be made to work with multiple ChangeStream impls for both storage cogs and custom garbage collection

@codecov

codecov Bot commented Sep 21, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.71%. Comparing base (dd12db4) to head (1b37d55).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #643      +/-   ##
==========================================
+ Coverage   90.68%   90.71%   +0.03%     
==========================================
  Files         115      115              
  Lines       22447    22522      +75     
==========================================
+ Hits        20356    20431      +75     
  Misses       2091     2091              
Components Coverage Δ
Rust Backend 94.33% <100.00%> (+0.02%) ⬆️
Rust Client 81.01% <ø> (ø)
Python Client 93.56% <ø> (ø)

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Comment on lines +46 to +62
fn write(&self, id: &ObjectId, size: u64, expires_at: Option<Timestamp>) {
for stream in self.streams.iter() {
stream.write(id, size, expires_at);
}
}

fn update(&self, id: &ObjectId, expires_at: Option<Timestamp>) {
for stream in self.streams.iter() {
stream.update(id, expires_at);
}
}

fn delete(&self, id: &ObjectId) {
for stream in self.streams.iter() {
stream.delete(id);
}
}

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

these aren't async trait methods but we might internally want to spawn them concurrently in case the underlying streams become sync by blocking on a long operation instead of returning optimistically

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WIth that being said, therefore every operation on ChangeStream should be blocking? Or am I misunderstanding this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants