[SERVER-13113] shell API does not validate write concern for empty batches Created: 10/Mar/14  Updated: 10/May/22

Status: Backlog
Project: Core Server
Component/s: Shell
Affects Version/s: 2.6.0-rc1
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Andreas Nilsson Assignee: DO NOT USE - Backlog - Platform Team
Resolution: Unresolved Votes: 0
Labels: 26qa, move-sa, platforms-re-triaged
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-15119 Accept a named "writeConcern" option ... Closed
is related to SERVER-12977 Write commands should error on empty ... Closed
Operating System: ALL
Steps To Reproduce:

// The following should return an invalid write concern error
var bulkOp = db.coll.initializeOrderedBulkOp();
bulkOp.execute({w:{a:1}})

Participants:

 Description   

If you create a bulk operation with an empty batch and execute it, the API returns a valid BulkWriteResult but there is no validation of the argument to execute.

We should be consistent with parameter validation regardless of backend execution.



 Comments   
Comment by Steven Vannelli [ 10/May/22 ]

Moving this ticket to the Backlog and removing the "Backlog" fixVersion as per our latest policy for using fixVersions.

Generated at Thu Feb 08 03:30:40 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.