[SERVER-28040] Fix maxTimeMS/readPref/readConcern for sharded view query Created: 17/Feb/17 Updated: 06/Dec/17 Resolved: 05/Apr/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying, Sharding |
| Affects Version/s: | 3.4.2 |
| Fix Version/s: | 3.5.6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Storch | Assignee: | James Wahlin |
| Resolution: | Done | Votes: | 0 |
| Labels: | read-only-views | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Backport Requested: |
v3.4
|
||||||||||||
| Steps To Reproduce: | Start a one-shard cluster, then run the following against the mongos:
|
||||||||||||
| Sprint: | Query 2017-03-27, Query 2017-04-17 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
When a sharded query on a view with maxTimeMS is rewritten on mongos to a query over the view's backing collection, the maxTimeMS is discarded. The consequence is that the maxTimeMS is not enforced for a sharded queries over views. This is true for both views on sharded and unsharded collections. MaxTimeMS does work, however, for queries against a view delivered directly to mongod. |
| Comments |
| Comment by Githook User [ 05/Apr/17 ] |
|
Author: {u'username': u'jameswahlin', u'name': u'James Wahlin', u'email': u'james.wahlin@10gen.com'}Message: |