[JAVA-1485] Ensure slaveOk property is set correctly for all uses of query protocol Created: 26/Sep/14  Updated: 31/Mar/15  Resolved: 17/Oct/14

Status: Closed
Project: Java Driver
Component/s: None
Affects Version/s: None
Fix Version/s: 3.0.0

Type: Task Priority: Major - P3
Reporter: Ross Lawley Assignee: Ross Lawley
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Review use of `slaveOk` in 3.0

  • URI String
  • DBCursor.addOption - when does it impact readPreference?


 Comments   
Comment by Jeffrey Yemin [ 31/Mar/15 ]

Closing all resolved 3.0.0 issues, as 3.0.0 has been tagged and released.

Comment by Githook User [ 30/Jan/15 ]

Author:

{u'username': u'rozza', u'name': u'Ross Lawley', u'email': u'ross.lawley@gmail.com'}

Message: Ensuring slaveOK is passed to QueryProtocol versions of operations

JAVA-1485
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/0aab478581ebeda30ed3bd92cb25b74b57b0ca31

Comment by Githook User [ 17/Oct/14 ]

Author:

{u'username': u'rozza', u'name': u'Ross Lawley', u'email': u'ross.lawley@gmail.com'}

Message: Ensuring slaveOK is passed to QueryProtocol versions of operations

JAVA-1485
Branch: 3.0.x
https://github.com/mongodb/mongo-java-driver/commit/0aab478581ebeda30ed3bd92cb25b74b57b0ca31

Comment by Jeffrey Yemin [ 07/Oct/14 ]

One thing I just saw: The ReadOperation implementations that use QueryProtocol don't set slaveOk on it if readPreference.isSlaveOk()

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