[SERVER-78100] [CQF] Reorder sargable nodes to better support merging Created: 14/Jun/23 Updated: 29/Oct/23 Resolved: 18/Aug/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: | Svilen Mihaylov (Inactive) | Assignee: | Jess Balint |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | QO 2023-06-26, QO 2023-07-10, QO 2023-07-24, QO 2023-08-07, QO 2023-08-21, QO 2023-09-04 |
| Participants: |
| Description |
|
Currently we reject sargable node merging if either one of them has a non-trivial disjunction (see intersectPartialSchemaReqMap). We may however have cases say with 3 sargable nodes where the first and last ones are trivial disjunctions while the middle one is not, and thus do not merge any of them.
We should add a rewrite to optionally reorder sargable nodes to support the best merging strategy. |
| Comments |
| Comment by Githook User [ 13/Jul/23 ] |
|
Author: {'name': 'Jess Balint', 'email': 'jess.balint@mongodb.com', 'username': ''}Message: |