[SERVER-12954] w parameter is not propagated correctly when calling getLastError on compatibility writeMode Created: 27/Feb/14 Updated: 11/Jul/16 Resolved: 14/Mar/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding, Shell |
| Affects Version/s: | 2.6.0-rc0 |
| Fix Version/s: | 2.6.0-rc2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Randolph Tan |
| Resolution: | Done | Votes: | 0 |
| Labels: | 26qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
Send this commands through a shell connect to mongos:
results with writeMode commands/legacy:
results with compatibility:
|
| Comments |
| Comment by Githook User [ 14/Mar/14 ] |
|
Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: Send resetError only when absolutely necessary. |
| Comment by Githook User [ 14/Mar/14 ] |
|
Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: Send resetError only when absolutely necessary. |
| Comment by Randolph Tan [ 28/Feb/14 ] |
|
This is a a problem in all cases - example is stand alone for simplicity. |
| Comment by Eric Milkie [ 28/Feb/14 ] |
|
So is it a problem only in the error case when you try to use a tagged write concern without a replica set? Or is it for all tagged write concerns in compat mode? |