[SERVER-22991] shell bulk api passes wrong flags when performing legacy inserts Created: 07/Mar/16  Updated: 06/Dec/22  Resolved: 03/Dec/21

Status: Closed
Project: Core Server
Component/s: Shell
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Mathias Stearn Assignee: Backlog - Server Tooling and Methods (STM) (Inactive)
Resolution: Won't Fix Votes: 0
Labels: move-stm
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Server Tooling & Methods
Participants:

 Description   

https://github.com/mongodb/mongo/blob/r3.3.2/src/mongo/shell/bulk_api.js#L883

It passes ordered as a bool, but the argument is an int32 flags field with 1 defined bit for continueOnError. This means it is always setting the bit to the opposite of what it should be. It probably doesn't have any effect today since the bulk api never does legacy inserts with more than one object to insert, but it could if we ever did.



 Comments   
Comment by Brooke Miller [ 03/Dec/21 ]

The shell is deprecated to external users, so please feel free to re-open if you are a core-db contributor and would like this feature for correctness testing purposes.

Generated at Thu Feb 08 04:02:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.