[SERVER-75715] Parameterize SBE plan cache for clustered collection scans and enable caching Created: 05/Apr/23 Updated: 29/Oct/23 Resolved: 23/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kevin Cherkauer | Assignee: | Kevin Cherkauer |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
The CollectionScanNode members minRecord and maxRecord are currently not parameterized in the SBE plan cache, therefore initial support for clustered collection scans in SBE ( This ticket is to add SBE plan cache parameterization of these members and enable caching of the plans. The result should be the current query's range bounds get substituted into the cached plan at runtime. |
| Comments |
| Comment by Githook User [ 23/May/23 ] |
|
Author: {'name': 'Kevin Cherkauer', 'email': 'kevin.cherkauer@mongodb.com', 'username': 'kevin-cherkauer'}Message: |