[SERVER-71801] [CQF] Validation for strong double alias Created: 02/Dec/22 Updated: 29/Oct/23 Resolved: 09/May/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: | Chi-I Huang |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | bonsai-ce | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Optimization
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | QO 2023-05-15 |
| Participants: |
| Description |
|
Follow up to Add validation logic based on Tag (e.g. selectivity clamped to 0-1, CE >= 0) |
| Comments |
| Comment by Githook User [ 09/May/23 ] |
|
Author: {'name': 'Chi-I Huang', 'email': 'chiihuang@mongodb.com', 'username': ''}Message: |
| Comment by Chi-I Huang [ 03/May/23 ] |
|
Keeping the data type StringDoubleAlias constexpr-friendly with validation is challenging. I tried 2 approaches: # Keep the strong alias constexpr -friendly. See this commit.
|
| Comment by Chi-I Huang [ 03/May/23 ] |
|
I am working on this ticket now. Right now I am working on keeping the whole struct StrongDoubleAlias as literal type, which is trickier than I expected. |