[SERVER-72906] Create client-side payload types for QE version 2 Created: 17/Jan/23 Updated: 29/Oct/23 Resolved: 20/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.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 | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Security 2023-01-23 |
| Participants: |
| Description |
|
For v2 of the QE protocol, the following payload types need to be defined in fle_field_schema.idl: 1. FLE2InsertUpdatePayloadV2 FLE2InsertUpdatePayloadV2 is mostly similar to FLE2InsertUpdatePayload, but the "c" field is replaced by an "l" field that encodes the ServerDerivedFromDataToken; a "k" field is added (type "long") to hold the contentionFactor, and the "g" field is changed to be an array of EdgeTokenSetV2. EdgeTokenSetV2 and FLE2FindEqualityPayloadV2 are similar to EdgeTokenSet and FLE2FindEqualityPayload, respectively, but with the "c" field replaced by an "l" field that holds the ServerDerivedFromDataToken. FLE2FindRangePayloadV2 is similar to FLE2FindRangePayload, but with the "payload" field changed to be of type FLE2FindRangePayloadEdgesInfoV2. |
| Comments |
| Comment by Githook User [ 20/Jan/23 ] |
|
Author: {'name': 'Erwin Pe', 'email': 'erwin.pe@mongodb.com', 'username': 'erwee'}Message: |