Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.3.0-rc0
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Query Execution
Backwards Compatibility:
Fully Compatible
Sprint:
QE 2026-01-05, QE 2025-12-22
Linked BF Score:
200
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

In scenarios where `$merge` specifies `whenNotMatched: "insert"` `whenMatched:"keepExisting"` we could use insert path ignoring duplicate errors. We use updates with `upsert` which is less performant and cannot be batched into a single `insertMany`.

The `whenMatched: "fail"` `whenNotMatched: "insert"` path uses insert, but may not use `insertMany`.

depends on

SERVER-115094 In MongoProcessInterface::insert return all error statuses instead of the first one

Closed

is related to

SERVER-113451 Duplicate-key errors cause excess slowness

Backlog

SERVER-115810 When $merge "on" field uses default value, it doesn't respect collation

In Progress

SERVER-115813 $merge doesn't forward collation to underlying updates

Closed

related to

SERVER-49952 check correctness and fix serverStatus metrics for $merge effects

Backlog

SERVER-115094 In MongoProcessInterface::insert return all error statuses instead of the first one

Closed

SERVER-116357 In $merge track InsertStats also for updates

Needs Scheduling

SERVER-116358 Add debug logs to $merge insert with backup strategy

Needs Scheduling

(3 related to)

Assignee:: Ivan Fefer
Reporter:: Asya Kamsky
Participants:: Asya Kamsky, Githook User, Ivan Fefer, Mihai Andrei
Votes:: 2 Vote for this issue
Watchers:: 10 Start watching this issue

Created:: Aug 08 2025 06:00:35 PM UTC
Updated:: Jan 08 2026 03:28:13 PM UTC
Resolved:: Jan 02 2026 12:11:27 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates