[SERVER-79041] [CQF] Decide how to deal with creating a global SBE slot for ShardFilterer Created: 17/Jul/23 Updated: 29/Oct/23 Resolved: 25/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: | Richard Hausman (Inactive) | Assignee: | Ben Shteinfeld |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Optimization
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | QO 2023-09-04 |
| Participants: |
| Description |
|
There are a couple of scenarios in which the necessity of creating an SBE slot depends on the characteristics of an SBE plan (for example, $now and shardFilter). This ticket will focus on shardFilter, but it remains a question for other scenarios. There are a couple of proposed solutions on how best to handle this scenario:
The task of this ticket is to decide what the best solution is and implement it for shard filtering, then to file a ticket to make the improvement in the other analogous cases. |
| Comments |
| Comment by Githook User [ 25/Aug/23 ] |
|
Author: {'name': 'Ben Shteinfeld', 'email': 'ben.shteinfeld@mongodb.com', 'username': 'bshteinfeld'}Message: This prevents queries against unsharded collections from unnecessarily registering a slot for the ShardFilterer. After this patch, the only situation in which a query would have an unused ShardFilterer is if the collection is sharded and the query contains an equality predicate on the shard key. |