Loading...

XML

Word

Printable

JSON

Documentation Changes:
Needed
Documentation Changes Summary:

Hide

1. If a read preference has been explicitly specified using `readPreference` in the connection string or `mongo.setReadPref()`, this `readPreference` will be applied to db.runCommand(), db.adminCommand(), and generally all db/rs/sh methods. If no read preference has been explicitly specified, the driver’s default is currently being used (i.e. a read preference of `primary`). This behavior differs from both the drivers’ behavior and the old shell’s behavior.

2. The `show dbs`/`show databases` and `show tables`/`show collections` commands always use a read preference of `primaryPreferred`, regardless of any otherwise specified read preference. This also differs from the old shell’s behavior.

Show
1. If a read preference has been explicitly specified using `readPreference` in the connection string or `mongo.setReadPref()`, this `readPreference` will be applied to db.runCommand(), db.adminCommand(), and generally all db/rs/sh methods. If no read preference has been explicitly specified, the driver’s default is currently being used (i.e. a read preference of `primary`). This behavior differs from both the drivers’ behavior and the old shell’s behavior. 2. The `show dbs`/`show databases` and `show tables`/`show collections` commands always use a read preference of `primaryPreferred`, regardless of any otherwise specified read preference. This also differs from the old shell’s behavior.

db.runCommand should inherit readPreference from the connection / db.getMongo as in the old shell.

To reproduce, connect to a secondary, set read preference of secondary in the mongo object, and try a db.runCommand(

{listDatabases: 1}

), that should work if the read preference is inherited.

causes

MONGOSH-1478 dropIndex() not working with readPreference=secondary in mongosh

is related to

COMPASS-6595 Initial ping command does not inherit connection readpreference