[COMPASS-7581] Investigate changes in PM-2554: Rich optimizer hints Created: 16/Jan/24 Updated: 22/Jan/24 Resolved: 17/Jan/24 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | No version |
| Type: | Investigation | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Developer Tools
|
||||
| Documentation Changes: | Not Needed | ||||
| Description |
|
Original Downstream Change Summary Adding syntax to force the query optimizer to select a particular plan needs to be exposed downstream and documented. Description of Linked TicketEpic Summary SummaryDefine the syntax and implement more sophisticated types of hints. Examples include hinting more complicated access paths (e.g. index intersection) or cross-collection hints for $lookup. MotivationEg., we don't yet support index intersection hints (SERVER-22741). Cast of Characters
DocumentationProduct Description |
| Comments |
| Comment by Rhys Howell [ 17/Jan/24 ] |
|
No devtools impact. Scope/technical design isn't complete yet, there's a chance we'll want to add something to mongosh eventually. |