[SERVER-81597] Change block based value comparison operations to take advantage of metadata Created: 29/Sep/23 Updated: 01/Nov/23 Resolved: 01/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ian Boros | Assignee: | Parker Felix |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Execution
|
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
When doing a block based numeric comparison, we can "short circuit" and mark an entire block as passing using the metadata in some cases. This only works on dense blocks (something we can only assume about the 'time' field), but it's worth implementing. If done right, this could act as a replacement for the 'wholeBucketFilter'. |
| Comments |
| Comment by Githook User [ 31/Oct/23 ] |
|
Author: {'name': 'Parker Felix', 'email': 'parker.felix@mongodb.com', 'username': 'parker-felix'}Message: |