[SERVER-39865] [FLE] Reject equality to null for encrypted field in match expression Created: 27/Feb/19 Updated: 29/Oct/23 Resolved: 05/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.9 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Nicholas Zolnierz | Assignee: | Nicholas Zolnierz |
| 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 2019-03-11 | ||||||||
| Participants: | |||||||||
| Description |
|
Mongocryptd should reject such queries, since we cannot guarantee the same semantics as if a field were unencrypted. The reason is because documents with a missing encrypted field will not be returned if mongocryptd were to mark the 'null' value for encryption. |
| Comments |
| Comment by Githook User [ 05/Mar/19 ] |
|
Author: {'name': 'Nick Zolnierz', 'username': 'nzolnierzmdb', 'email': 'nicholas.zolnierz@mongodb.com'}Message: |