[JAVA-1872] Deprecate PrimaryServerSelector in favor of new WritableServerSelector Created: 23/Jun/15  Updated: 07/Oct/15  Resolved: 24/Aug/15

Status: Closed
Project: Java Driver
Component/s: API, Cluster Management
Affects Version/s: 3.0.2
Fix Version/s: 3.1.0

Type: Improvement Priority: Minor - P4
Reporter: Jeffrey Yemin Assignee: Jeffrey Yemin
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

It's confusing that a PrimaryServerSelector instance does not behave identically to a ReadPreferenceServerSelector with a primary read preference. The latter treats clusters with a direct connection mode specially, while the former does not. To remove this confusion, we should deprecate PrimaryServerSelector and add a new WritableServerSelector that works the same. In others, a class rename that doesn't break compatibility.



 Comments   
Comment by Jeffrey Yemin [ 07/Oct/15 ]

Released in 3.1.0

Comment by Githook User [ 24/Aug/15 ]

Author:

{u'username': u'jyemin', u'name': u'Jeff Yemin', u'email': u'jeff.yemin@10gen.com'}

Message: Deprecated PrimaryServerSelector and replaced with WritableServerSelector, which more accurately describes its behavior, as its not equivalent to a ReadPreferenceServerSelector with primary read preference.

JAVA-1872
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/10486d2c8c764bf864bcdafaa02b35d7f3b98719

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