[SERVER-81861] [CQF] RIDIntersect implementer accesses RepititionEstimation physical property when it might be missing Created: 04/Oct/23 Updated: 29/Oct/23 Resolved: 05/Oct/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ben Shteinfeld | Assignee: | Ben Shteinfeld |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | QO 2023-10-16 | ||||||||
| Participants: | |||||||||
| Description |
|
jstests/sharding/update_compound_shard_key.js (run here) shows a query failure due to a uassert failing when referencing the value of RepetitionEstimate from a set of physical properties which is missing this property. This occurs in the implementer for RIDIntersectNode when optimized with an index target requirement. This ticket tracks work to check if this property exists before referencing it and provide a fallback value. |
| Comments |
| Comment by Githook User [ 04/Oct/23 ] |
|
Author: {'name': 'Ben Shteinfeld', 'email': 'ben.shteinfeld@mongodb.com', 'username': 'bshteinfeld'}Message: In the implementer for RIDIntersectNode, check if the set of physical |