[SERVER-37686] Wildcard index should not assume non-descending bounds when checking overlap with object type bracket Created: 19/Oct/18 Updated: 29/Oct/23 Resolved: 23/Oct/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance, Querying |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.5 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Bernard Gorman | Assignee: | Bernard Gorman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Query 2018-11-05 |
| Participants: |
| Description |
|
In boundsOverlapObjectTypeBracket we invariant that the OIL's bounds are always ascending or a point-interval. However, it is possible to reach this point after the bounds have been reversed and are now descending, if we are attempting to determine whether the wildcard index can support a projection on a query that is sorted in reverse order. |
| Comments |
| Comment by Githook User [ 23/Oct/18 ] |
|
Author: {'name': 'Bernard Gorman', 'email': 'bernard.gorman@gmail.com', 'username': 'gormanb'}Message: |