[SERVER-17158] sort component of internal plan cache key syntax is ambiguous Created: 03/Feb/15 Updated: 19/Sep/15 Resolved: 19/Mar/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | 3.0.0-rc7 |
| Fix Version/s: | 3.1.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Thomas Rueckstiess | Assignee: | James Wahlin |
| Resolution: | Done | Votes: | 0 |
| Labels: | neweng, pull-request | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Quint Iteration 3.1.1 | ||||||||
| Participants: | |||||||||
| Description |
|
The internal representation for the sort order of a plan cache key as defined in canonical_query.cpp:269-276 is ambiguous because it does not use any separators for multiple keys. These two queries produce the same cache key and could therefore incorrectly use a wrong cached plan:
Both produce the internal key: an[eqb,gta]~aaab. This could be avoided with a separator between multiple sort keys, e.g.
|
| Comments |
| Comment by Githook User [ 19/Mar/15 ] |
|
Author: {u'name': u'james.wahlin@10gen.com', u'email': u'james.wahlin@10gen.com'}Message: Closes #938 Signed-off-by: David Storch <david.storch@10gen.com> |