[SERVER-44418] Optimise distinct queries to use DISTINCT_SCAN in the presence of compound hashed index. Created: 05/Nov/19 Updated: 29/Oct/23 Resolved: 16/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.3 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Arun Banala | Assignee: | Arun Banala |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Query 2019-11-18, Query 2019-12-16, Query 2019-12-30, Query 2020-01-13, Query 2020-01-27 |
| Participants: |
| Comments |
| Comment by Githook User [ 16/Jan/20 ] |
|
Author: {'name': 'Arun Banala', 'username': 'banarun', 'email': 'arun.banala@mongodb.com'}Message: create mode 100644 jstests/core/distinct_with_hashed_index.js |