-
Notifications
You must be signed in to change notification settings - Fork 8
DOC-614 | Added readOwnWrites
option for UPSERT operations
#409
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
Conversation
Deploy Preview Available Via |
|
||
When the option is set to `false`, an `UPSERT` operation processes its inputs | ||
in batches. A batch has normally 1000 inputs, so it can lead to a faster execution. | ||
However, when using batches, the `UPSERT` operation cannot observe its own writes. |
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.
for the most part? If the modifications happen to be in two different batches, then I suppose they are observed, but this is of course highly unreliable. Maybe insert a "basically"?
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.
How would you rephrase it?
site/content/3.12/release-notes/version-3.12/whats-new-in-3-12.md
Outdated
Show resolved
Hide resolved
site/content/3.12/release-notes/version-3.12/whats-new-in-3-12.md
Outdated
Show resolved
Hide resolved
site/content/3.12/release-notes/version-3.12/whats-new-in-3-12.md
Outdated
Show resolved
Hide resolved
site/content/3.12/release-notes/version-3.12/whats-new-in-3-12.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Simran <Simran-B@users.noreply.github.com>
Description
Added
readOwnWrites
option for UPSERT operations.Upstream PRs