[SERVER-72919] Implement v2 changes to Queryable Encryption Inserts Created: 17/Jan/23 Updated: 29/Oct/23 Resolved: 14/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-06, Security 2023-02-20 |
| Participants: |
| Description |
|
In v2 of the QE protocol, encrypted inserts must reject old insert/update payload formats and start accepting FLE2InsertUpdatePayloadV2. Depending on whether the encrypted field is equality or range indexed, the corresponding FLE2InsertUpdatePayloadV2 shall be converted to either FLE2EqualityIndexedValueV2 or FLE2RangeIndexedValueV2 on-disk formats, before inserting to the collection. The tags and counter values shall be obtained using the v2 EmuBinary algorithm, and documents inserted to the ESC must use the new document formats. |
| Comments |
| Comment by Githook User [ 14/Feb/23 ] |
|
Author: {'name': 'Erwin Pe', 'email': 'erwin.pe@mongodb.com', 'username': 'erwee'}Message: |