-
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-2843): implement sessions advanceClusterTime method #2920
Conversation
Co-authored-by: Neal Beeken <[email protected]>
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
!clusterTime.signature || | ||
clusterTime.signature.hash?._bsontype !== 'Binary' || | ||
(typeof clusterTime.signature.keyId !== 'number' && | ||
clusterTime.signature.keyId?._bsontype !== 'Long') // apparently we decode the key to number? |
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.
@nbbeeken Just bringing your attention to this change
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.
Just so I do not block this PR: looks correct to me.
Remind me to tell you the deeper issue here / file a ticket next week, has to do with BSON promote*
options I think.
Description
NODE-2843
What changed?
Implemented the advanceClusterTime session method, refactored internal helper function for naming consistency