[JAVA-658] DBTCPConnector ignores readprefs for combination of legacy settings Created: 01/Oct/12 Updated: 08/Jan/13 Resolved: 20/Oct/12 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | API |
| Affects Version/s: | 2.9.0 |
| Fix Version/s: | 2.9.2, 2.10.0 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Matt Schemmel | Assignee: | Jeffrey Yemin |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Minor Change |
| Description |
|
The method DBTCPConnector#call incorrectly deals with read preferences when:
The beginning of the method tests the passed readPref against ReadPreference.primary() using object equality, so the inferred use of ReadPreference.secondaryPreferred() for slaveOk queries is not triggered. The default read preference on the mongo is ReadPreference.primary() in the v2.9.0 dist, so this bug only affects code written against older releases that explicitly set ReadPreference.PRIMARY at some point. |
| Comments |
| Comment by auto [ 08/Jan/13 ] |
|
Author: {u'date': u'2012-10-01T21:39:10Z', u'email': u'jeff.yemin@10gen.com', u'name': u'Jeff Yemin'}Message: |
| Comment by auto [ 08/Jan/13 ] |
|
Author: {u'date': u'2012-10-01T21:39:10Z', u'email': u'jeff.yemin@10gen.com', u'name': u'Jeff Yemin'}Message: |
| Comment by auto [ 10/Oct/12 ] |
|
Author: {u'date': u'2012-10-01T14:39:10-07:00', u'email': u'jeff.yemin@10gen.com', u'name': u'Jeff Yemin'}Message: |
| Comment by auto [ 09/Oct/12 ] |
|
Author: {u'date': u'2012-10-01T14:39:10-07:00', u'email': u'jeff.yemin@10gen.com', u'name': u'Jeff Yemin'}Message: |
| Comment by Jeffrey Yemin [ 01/Oct/12 ] |
|
Good find Matt. Thanks for the report. |