-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(NODE-4484): add experimental support for disambiguatedPaths in change stream documents #3365
Conversation
eee0b08
to
a065cfb
Compare
Just linking to the tests passing in evg against latest: https://evergreen.mongodb.com/task_log_raw/mongo_node_driver_next_ubuntu_18.04_erbium_test_latest_replica_set_patch_f28ba0de3bc925267a185965eb971ecf91bc2680_62fd236be3c3313be42d354a_22_08_17_17_20_44/0?type=T#L838 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
a4ab9ff
to
565fd4f
Compare
CSFLE pinned commit tests will fail after the rebase of mongodb/libmongocrypt#443 - the sha1 doesn't exist anymore after the squash/rebase of that PR but does not affect this PR. |
@baileympearson Should this really be a "test" and not a "feat" commit? Experimental or not, it's still not a test-only commit. I also noticed a curious failure - a cursor exhausted test - has that been already investigated and logged a flaky issue? |
565fd4f
to
eadb104
Compare
Description
What is changing?
This PR is a POC PR for mongodb/specifications#1292.
A new field is supported on change stream update documents on servers >= 6.1.0 when
showExpandedEvents
is true. This PR adds new spec tests for the new field and documents the new property on theUpdateDescription
type, marked as experimental.A follow up ticket has been filed to remove the experimental tag after the 6.1 release - https://jira.mongodb.org/browse/NODE-4554.
Is there new documentation needed for these changes?
No.
What is the motivation for this change?
https://jira.mongodb.org/browse/DRIVERS-2344.
Double check the following
npm run check:lint
script<type>(NODE-xxxx)<!>: <description>