Investigate apparent regression in classic engine IDHACK
(SERVER-68110)
|
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Major - P3 |
| Reporter: | Colin Stolley | Assignee: | Colin Stolley |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Sprint: | QE 2023-05-15 | ||||
| Participants: | |||||
| Description |
|
We can avoid creating a plan cache key for IDHACK queries since they aren't cached anyway. We still need the query hash, but that's always the same, so we can stash that in a static local to avoid recomputing it for each query. |
| Comments |
| Comment by Colin Stolley [ 05/Apr/23 ] |
|
This turns out to have a fatal problem where we can't memoize the query hash for all IDHACK queries because projections change the hash. |