[SERVER-66657] FLE query analysis bans validators with valid $jsonSchema that is not at the top level Created: 23/May/22 Updated: 27/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Davis Haupt (Inactive) | Assignee: | Backlog - Query Integration |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | query-product-scope-1, query-product-urgency-3, query-product-value-2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Integration
|
| Participants: |
| Description |
|
This is a bug that only affects FLE 1. As mentioned in SERVER-66656, $jsonSchema is right now assumed to be the only operator in a validator if it is present in a validator. That ticket tracks a way that invalid validators can still pass through. This ticket tracks the flip side, where there are ways to nest $jsonSchema under $or or $and operators that are potentially valid but that we don't currently support. |
| Comments |
| Comment by Katya Kamenieva [ 23/Feb/23 ] |
|
This is current limitation in FLE1, not a regression. According to cynthia.braund@mongodb.com we do not hear about this too often from the users. Backloging for now. |
| Comment by Asya Kamsky [ 23/Feb/23 ] |
|
We absolutely should allow this and pretty sure we used to so is this a regression? |
| Comment by Xiaochen Wu [ 15/Dec/22 ] |
|
User should be able to combine JSON Schema validation with query operator validation. |