Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Consistent top-level timestamps option for bulkWrite operations #14536

Closed
2 tasks done
vkarpov15 opened this issue Apr 25, 2024 · 0 comments · Fixed by #14546
Closed
2 tasks done

Consistent top-level timestamps option for bulkWrite operations #14536

vkarpov15 opened this issue Apr 25, 2024 · 0 comments · Fixed by #14546
Milestone
8.3.4

Comments

@vkarpov15
Copy link
Collaborator

Prerequisites

  • I have written a descriptive issue title
  • I have searched existing issues to ensure the bug has not already been reported

Mongoose version

7.x, 8.x

Node.js version

Doesn't matter

MongoDB server version

Doesn't matter

Typescript version (if applicable)

No response

Description

Re: #14513 (comment), only insertOne supports timestamps option, other bulkWrite operators like updateOne and updateMany do not.

Steps to Reproduce

See description

Expected Behavior

All bulkWrite operators should support timestamps
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
8.3.4
Development

Successfully merging a pull request may close this issue.

Improved timestamps option handling in bulkWrite sderrow/mongoose
1 participant
@vkarpov15