[SERVER-14617] Cardinality Histogram for Query Planner Created: 18/Jul/14 Updated: 01/Oct/15 Resolved: 01/Oct/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Osmar Olivo | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
Cardinality Histogram for indexes, similar to what a lot of relational databases have. This will allow for the query planner to more intelligently decide when it is optimal to use certain indexes over others on a per query basis (Not simply based off a cached value that might be a one off). This will allow for more effective use of index intersection, indexes, and tablescans (where appropriate) |
| Comments |
| Comment by David Storch [ 01/Oct/15 ] |
|
Resolving as a duplicate of SERVER-20619, since the newer ticket is slightly more general. |