Repository navigation
feat(database): add find cursor iteration - #17
Merged
Merged
Conversation
Expose optional per-document iteration and decode support on find results so consumers can handle individual malformed documents without aborting the complete result set, with matching mock behavior and tests.
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This change adds cursor-style iteration support for database find operations through the new
CursorResultInterface. Previously, consumers could only decode the entire result set at once withAll(), which meant a single malformed document could fail the entire query result.With per-document iteration (
Next,Decode, andClose), callers can now handle decode failures on individual records while continuing to process valid documents. This improves resilience for workloads that operate on partially inconsistent or evolving data without sacrificing the rest of the result set.The MongoDB implementation and mock database were both updated to support the new interface, ensuring consistent behavior between production code and tests. Additional test coverage verifies that:
Overall, this improves fault tolerance, makes data processing workflows more flexible, and enables more realistic testing of streaming query behavior.