[SERVER-34846] Covered index with collated field returns incorrect result when collation not involved in match or sort Created: 04/May/18 Updated: 29/Oct/23 Resolved: 31/Jul/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.17, 3.6.8, 4.0.2, 4.1.2 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Asya Kamsky | Assignee: | Ian Boros |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | bkp, collation, neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Backport Requested: |
v4.0, v3.6, v3.4, v3.2
|
||||
| Sprint: | Query 2018-06-18, Query 2018-07-02, Query 2018-07-16, Query 2018-07-30, Query 2018-08-13 | ||||
| Participants: | |||||
| Description |
|
It appears that when covered index can be used, but collation isn't involved in match or sort then the strings from covered index query are returned without being looked up.
|
| Comments |
| Comment by Githook User [ 23/Aug/18 ] | ||||
|
Author: {'name': 'Ian Boros', 'email': 'ian.boros@10gen.com'}Message: | ||||
| Comment by Githook User [ 23/Aug/18 ] | ||||
|
Author: {'name': 'Ian Boros', 'email': 'ian.boros@10gen.com'}Message: (cherry picked from commit 7f442763c791873d74bea5c0c6e01812933deb38) | ||||
| Comment by Githook User [ 23/Aug/18 ] | ||||
|
Author: {'name': 'Ian Boros', 'email': 'ian.boros@10gen.com'}Message: (cherry picked from commit 7f442763c791873d74bea5c0c6e01812933deb38) | ||||
| Comment by Githook User [ 31/Jul/18 ] | ||||
|
Author: {'name': 'Ian Boros', 'email': 'ian.boros@10gen.com'}Message: | ||||
| Comment by Asya Kamsky [ 04/May/18 ] | ||||
| ||||
| Comment by Asya Kamsky [ 04/May/18 ] | ||||
|
Note that the behavior cannot be reproduced if sort is added EVEN if it's sort on int (with or without collation specified).
|