Skip to content

DOCS-5284: improves upsert/upsertFields wording #2292

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-5284: improves upsert/upsertFields wording #2292

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
7 changes: 4 additions & 3 deletions source/includes/options-mongoimport.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -309,8 +309,8 @@ description: |
:program:`mongod`'s performance.

.. versionchanged:: 3.0.0
{{role}} is no longer needed when specifying upserts. Use
:option:`--upsertFields`, which produces the same behavior.
:option:`--upsertFields` now implies {{role}}. As such, you may
prefer to use :option:`--upsertFields` instead of {{role}}.
optional: true
---
program: mongoimport
Expand All @@ -327,7 +327,8 @@ description: |
.. versionchanged:: 3.0.0
Modifies the import process to update existing objects in the
database if they match based on the specified fields, while
inserting all other objects.
inserting all other objects. You do not need to use :option:`--upsert`
with {{role}}.

If you do not specify a field, {{role}} will upsert on the basis of
the ``_id`` field.
Expand Down