[SERVER-50712] Handle shard filtering in SBE Created: 02/Sep/20 Updated: 29/Oct/23 Resolved: 01/Dec/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | David Storch | Assignee: | Eric Cox (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Query 2020-11-30, Query 2020-12-14 | ||||||||
| Participants: | |||||||||
| Description |
|
If the slot-based execution engine is enabled on a particular shard, then the planner may produce plans that involve the SHARDING_FILTER QuerySolutionNode. Today, the system will simply uassert() if it encounters a SHARDING_FILTER node when converting the QuerySolution to an SBE plan. We need to extend SBE to be capable of doing shard-filtering at runtime in order for it to be used in sharded clusters. |
| Comments |
| Comment by Githook User [ 01/Dec/20 ] |
|
Author: {'name': 'Eric Cox', 'email': 'eric.cox@mongodb.com', 'username': 'ericox'}Message: |