Skip to content

DOCS-4197 - explanation of applyOps flag #2063

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

Closed
wants to merge 1 commit into from
Closed

DOCS-4197 - explanation of applyOps flag #2063

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions source/reference/command/applyOps-field.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,4 +19,15 @@ name: preCondition
type: array
position: 2
description: "An array of documents that contain the conditions that must be true in order to apply the oplog entry. Each document contains a set of conditions, as described in the next table."
---
object:
name: applyOps
type: dbcommand
field:
optional: true
type: field
name: alwaysUpsert
type: array
position: 2
description: "A flag that indicates whether to apply update operations in the oplog as upserts. ``true`` indicates that updates will be applied as upserts, preventing cases in which updates followed by deletes will cause failures. This is the same manner in which secondaries perform normal replication, as operations from the replicated oplog may have already been executed. ``false`` indicates that updates will be applied as they are. This is the same manner in which secondaries perform initial syncs. ``true`` by default."
...