[SERVER-29913] bulk_api.js should use runCommand() rather than DBQuery().next() Created: 28/Jun/17  Updated: 30/Oct/23  Resolved: 24/Aug/17

Status: Closed
Project: Core Server
Component/s: Shell, Testing Infrastructure
Affects Version/s: None
Fix Version/s: 3.5.13

Type: Improvement Priority: Major - P3
Reporter: Mathias Stearn Assignee: Max Hirschhorn
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-30686 Integrate retryWrites into mongo shel... Closed
Related
is related to SERVER-29277 Two Phase Drops: implement dropDataba... Closed
is related to SERVER-29928 invalid_db_name.js should test server... Closed
Backwards Compatibility: Fully Compatible
Sprint: TIG 2017-09-11
Participants:

 Description   

The real work here is fixing the DatabaseDropPending workarounds from implicitly_retry_on_database_drop_pending.js to work with runCommand() rather than just DBQuery.next(). Another minor dependency is removing the assert that the dbname is valid from DBClientWithCommands::runCommandWithTarget() so that we can test how the server behaves with invalid dbnames.



 Comments   
Comment by Ramon Fernandez Marina [ 24/Aug/17 ]

Author:

{'username': u'visemet', 'name': u'Max Hirschhorn', 'email': u'max.hirschhorn@mongodb.com'}

Message:SERVER-29913 Use runCommand() in bulk_api.js for performing writes.

Also changes the function override for Mongo.prototype.runCommand() in
implicitly_retry_on_database_drop_pending.js to handle the "insert" and
"update" command responses.
Branch:master
https://github.com/mongodb/mongo/commit/a797fef88f2eba8701618dcad8546ac5ec2036c2

Comment by Max Hirschhorn [ 22/Aug/17 ]

Changing the behavior of DBClientWithCommands::runCommandWithTarget() was done already by Mathias as part of SERVER-29928.

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