[SERVER-19609] Put shard version on OperationContext Created: 27/Jul/15 Updated: 19/Sep/15 Resolved: 31/Jul/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.7 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | David Storch |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Quint Iteration 7 |
| Participants: |
| Description |
|
Commands which go through the NetworkInterface will need to be made to transmit the desired shard version of the namespace they operate on, while the mongod side of these commands will need to be made to always parse that information. This ticket is to put shard version information on the OperationContext. |
| Comments |
| Comment by Githook User [ 31/Jul/15 ] |
|
Author: {u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}Message: This will be useful when mongos starts sending shard version as a find command parameter. |
| Comment by Kaloian Manassiev [ 28/Jul/15 ] |
|
Making cluster client cursor shard version aware depends on this, so it makes sense to do it as part of that work. |