feat(NODE-6676): add support for nsType in change stream create events
#4431
+238
−0
Conversation
This file contains 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
nbbeeken
requested changes
Feb 24, 2025
nbbeeken
added
the
Primary Review
Co-authored-by: Neal Beeken <neal.beeken@mongodb.com>
nbbeeken
approved these changes
Feb 24, 2025
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
What is changing?
Support has been added for nsType in change stream create events.
CI will be better when #4426 merges, but you can confirm that the latest builds only fail with the expected CSFLE failures and that the new nsType change stream tests pass. Ex: https://parsley.mongodb.com/evergreen/mongo_node_driver_next_rhel80_large_Node20_test_latest_sharded_cluster_patch_cb6a7ba61c112738e08c90330da491a3ab8fdf36_67bcb63cad81aa0007a87119_25_02_24_18_11_14/0/task?bookmarks=0,8904&shareLine=972
Is there new documentation needed for these changes?
No.
What is the motivation for this change?
Double check the following
npm run check:lintscripttype(NODE-xxxx)[!]: descriptionfeat(NODE-1234)!: rewriting everything in coffeescript