[SERVER-8219] empty tag sets [{}] asserts with primary read preference Created: 17/Jan/13 Updated: 11/Jul/16 Resolved: 01/Feb/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Client |
| Affects Version/s: | None |
| Fix Version/s: | 2.4.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | A. Jesse Jiryu Davis | Assignee: | Randolph Tan |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
In jsTests, with a ReplicaSetConnection:
... always results in:
[{}] should be treated the same as null, but apparently it's treated some other way. |
| Comments |
| Comment by auto [ 01/Feb/13 ] |
|
Author: {u'date': u'2013-01-24T16:07:18Z', u'email': u'randolph@10gen.com', u'name': u'Randolph Tan'}Message: |
| Comment by Randolph Tan [ 23/Jan/13 ] |
|
Did a quick survey: Ruby: allowed So I am going to proceed to allow {} tag set for primary. |
| Comment by Randolph Tan [ 23/Jan/13 ] |
|
The specs says that specifying tags for primary is an error. So, the C++ driver treats it as an error if read preference is primary and the tag field exists. Will check with how the other drivers deal with this to be consistent. |
| Comment by A. Jesse Jiryu Davis [ 17/Jan/13 ] |
|
My local current version of read_pref_cmd.js |