[SERVER-72931] Implement v2 changes to Queryable Encryption Deletes Created: 17/Jan/23 Updated: 29/Oct/23 Resolved: 27/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Erwin Pe | Assignee: | Erwin Pe |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Security
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Security 2023-02-20, Security 2023-03-06 |
| Participants: |
| Description |
|
In v2 of the QE protocol, encrypted deletes no longer make use of deleteTokens in encryptionInformation, and no longer needs to perform state collection insertions. Much of the processing logic for removed fields can therefore be removed. As with v2 finds, v1 payload types (FLE2FindEqualityPayload or FLE2FindRangePayload) should be rejected with an error when encountered in the query part. |
| Comments |
| Comment by Githook User [ 24/Feb/23 ] |
|
Author: {'name': 'Erwin Pe', 'email': 'erwin.pe@mongodb.com', 'username': 'erwee'}Message: |